Multi-Carrier Rel-18

 RAN1#109-e

9.10   Multi-carrier enhancements for NR

Please refer to RP-220834 for detailed scope of the WI.

R1-2204397        Work plan for Multi-carrier enhancements            NTT DOCOMO, INC.

9.10.1     Multi-cell PUSCH/PDSCH scheduling with a single DCI

R1-2203276        On multi-cell PUSCH/PDSCH scheduling with a single DCI              Nokia, Nokia Shanghai Bell

·        Proposal 2.1: Focus the discussions in the early WI phase on overarching principles for multi-cell PDSCH/PUSCH scheduling incl. overall scheduling framework for a cell, intended application scenarios and multi-cell DCI design framework assumptions before discussing the details of the multi-cell DCI content DCI field per DCI field.

·        Proposal 2.2: The Rel-15…Rel-17 cross-carrier scheduling framework applies as-is; The multi-cell DCI is considered the scheduling DCI, and the PDCCH transmitting it is considered the scheduling PDCCH and the scheduled PxSCH processing and timelines as specified for cross-carrier scheduling are used the same way as with single-cell DCI.

·        Proposal 3.1: Introduce new DCI formats 0_X (e.g. 0_3) for multi-cell PUSCH scheduling with a single DCI and 1_X (e.g. 1_3) for multi-cell PDSCH scheduling with a single DCI.

·        Proposal 3.2.1: Each scheduled cell can be configured to be scheduled by a multi-cell DCI in one and only one scheduling cell.

·        Proposal 3.2.2: Support the combination of multi-cell DCI scheduling and single-cell DCI scheduling (using legacy DCI formats) for PDSCH (or PUSCH) of a serving cell.

·        Proposal 3.2.3: For a scheduled cell,

o   support multi-cell DCI and single-cell DCI scheduling from one scheduling cell

o   support multi-cell DCI scheduling from one scheduling cell and single-cell DCI self-scheduling

o   do not support multi-cell DCI and single-cell DCI cross-carrier scheduling from more than one (other) scheduling cell.

·        Proposal 3.3.1: The multi-cell PUSCH scheduling with a single DCI it to be restricted within a single (PUCCH) cell group.

·        Proposal 3.3.2: Support a maximum of 4 cells that can be scheduled simultaneously by a single DCI.

·        Proposal 3.3.3: To limit the DCI size, the maximum number of cells that can be scheduled should be based on RRC configuration (i.e. from the set of {2,3,4}).

·        Proposal 3.3.4: Support separate configurations for the multi-cell scheduling DCI for PDSCH and PUSCH.

·        Proposal 3.3.5: The scheduled cells are indicated in a DCI field pointing to a table of scheduled cell(s).

o   The table of scheduled cell(s) to be scheduled is RRC configured for the UE.

o   Support separate table configurations for the multi-cell scheduling DCI for PDSCH and PUSCH.

·        Proposal 3.3.6: Support the monitoring for at least two multi-cell DCIs for PDSCH (or PUSCH) on different scheduling cells within a PUCCH cell group, where each of the multi-cell DCIs can schedule a different (non-overlapping) subgroup of cells within a PUCCH cell group.

·        Proposal 3.4.2: The multi-cell DCI size(s) are not counted towards the DCI size budget (for DCI formats scrambled by C-RNTI) per serving cell and not considered in the related serving cell specific DCI size alignment procedure. Instead, the gNB will guarantee that across the K cells applicable for multi-cell DCI scheduling that the total budget of 3*K DCI sizes is not exceeded.

·        Proposal 3.5.1: The design of the MC-DCI should allow for optimization of the MC-DCI size when all cells within the MC-DCI have some commonalities, e.g. same numerology and duplexing mode. Note these optimizations need not be limited to intra-band case.

·        Proposal 3.5.2: For mixed SCS multi-cell DCI scheduling operation, apply the Rel-16 processing timelines as if the multi-DCI represented individual single-cell DCI, each scheduling a different carrier.

Decision: The document is noted.

R1-2203135         Discussion on multi-cell PUSCH/PDSCH scheduling with a single scheduling DCI               Huawei, HiSilicon

R1-2203207         Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI               ZTE

R1-2203346         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI Spreadtrum Communications

R1-2203448         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI CATT

R1-2203583         Discussion on multi-cell scheduling vivo

R1-2203664         Discussion on multi-cell scheduling with a single DCI              China Telecom

R1-2203688         Discussion on Multi-cell PXSCH scheduling with a single DCI              NEC

R1-2203706         Discussion on multi-cell scheduling via a single DCI  Lenovo

R1-2203800         Discussion on the design of multi-cell scheduling with a single DCI       xiaomi

R1-2203842         Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI               Langbo

R1-2203925         Multi-cell PUSCH/PDSCH scheduling with a single DCI         Samsung

R1-2204026         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI OPPO

R1-2204087         Multi-cell scheduling with a single DCI        InterDigital, Inc.

R1-2204186         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI CAICT

R1-2204262         On multi-cell PUSCH/PDSCH scheduling with a single DCI    Apple

R1-2204324         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI CMCC

R1-2204398         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI NTT DOCOMO, INC.

R1-2204631         Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI               LG Electronics

R1-2204697         On multi-cell PUSCH/PDSCH scheduling with a single DCI    MediaTek Inc.

R1-2204816         Discussions on multi-cell scheduling with a single DCI             Intel Corporation

R1-2204865         Multi-cell PUSCH/PDSCH scheduling with a single DCI         Charter Communications

R1-2204888         Multi-cell PUSCH/PDSCH scheduling with a single DCI         Ericsson

R1-2205051         Multi-cell PUSCH and PDSCH scheduling with a single DCI  Qualcomm Incorporated

R1-2205073         Discussion on Multicarrier scheduling with a single DCI          FGI

R1-2205088         Consideration on multi-cell PUSCH/PDSCH scheduling with a single DCI               Fujitsu Limited

[109-e-R18-MC_Enh-01] – Haipeng (Lenovo)

Email discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI by May 20

-        Check points: May 12, May 18, May 20

R1-2205234        Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI       Moderator (Lenovo)

From May 11^th GTW session

Agreement

Agree the following terminologies ONLY for convenience of discussion:

·        DCI format 0_X is used for scheduling multiple PUSCHs on multiple cells with one PUSCH per cell

·        DCI format 1_X is used for scheduling multiple PDSCHs on multiple cells with one PDSCH per cell.

The above does not imply introducing new DCI format(s) at this point.

Agreement

·        Different TBs are scheduled on different cells by DCI format 0_X.

·        Different TBs are scheduled on different cells by DCI format 1_X.

Agreement

Fallback DCI (i.e., DCI formats 0_0 and 1_0) does not support multi-cell scheduling.

Agreement

The DCI for multi-cell scheduling is monitored only in USS set.

Agreement

·        PDSCH cannot be scheduled by DCI format 0_X.

·        PUSCH cannot be scheduled by DCI format 1_X.

Agreement

·        All the co-scheduled cells by a DCI format 1_X and the scheduling cell are included in the same PUCCH group.

·        FFS: All the co-scheduled cells by a DCI format 0_X and the scheduling cell are included in the same [cell or PUCCH group].

Decision: As per email decision posted on May 14^th,

Agreement

·        DCI format 0-X/1-X on a scheduling cell can be used to schedule PUSCHs/PDSCHs on multiple cells including the scheduling cell.

·        DCI format 0-X/1-X on a scheduling cell can be used to schedule PUSCHs/PDSCHs on multiple cells not including the scheduling cell.

Agreement

·        For a UE, the maximum number of cells scheduled by a DCI format 0_X can be same or different to the maximum number of cells scheduled by a DCI format 1_X.

Working Assumption

·        All HARQ-ACK codebook types (Type-1/2/3) are applicable when multi-carrier PDSCH scheduling is configured.

R1-2205235         Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI               Moderator (Lenovo)

R1-2205236        Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI       Moderator (Lenovo)

From May 17^th GTW session

Agreement

·        One value for the maximum number of co-scheduled cells by a DCI format 0_X in Rel-18 is selected from {3, 4, 8}.

·        For a UE, the maximum number of co-scheduled cells by a DCI format 0_X can be smaller than or equal to the maximum number supported in Rel-18.

Agreement

·        One value for the maximum number of co-scheduled cells by a DCI format 1_X in Rel-18 is selected from {3, 4, 8}.

·        For a UE, the maximum number of co-scheduled cells by a DCI format 1_X can be smaller than or equal to the maximum number supported in Rel-18.

Agreement

·        (Working assumption) DCI format 0_X/1_X is a new DCI format for multi-cell scheduling

·        DCI format 0_X can be used for single cell PUSCH scheduling.

·        DCI format 1_X can be used for single cell PDSCH scheduling.

·        FFS: UE monitors one of or both multi-cell scheduling DCI and legacy single cell scheduling DCI for a scheduled

R1-2205486         Feature lead summary#4 on multi-cell PUSCH/PDSCH scheduling with a single DCI               Moderator (Lenovo)

R1-2205487        Feature lead summary#5 on multi-cell PUSCH/PDSCH scheduling with a single DCI       Moderator (Lenovo)

Decision: As per email decision posted on May 21^st,

Agreement

• DCI format 0-X/1-X can be transmitted on PCell.
• DCI format 0-X/1-X can be transmitted on a SCell at least when the DCI format 0-X/1-X does not schedule PUSCH/PDSCH on PCell.
• FFS whether a DCI format 0-X/1-X can be transmitted on an SCell if the DCI format 0-X/1-X schedules PUSCH/PDSCH on PCell.

Agreement

Further study DCI size budget including below options for multi-cell scheduling DCI:

• Option 1: Existing DCI size budget is maintained per scheduled cell.
• Alt 1-1: DCI size budget is maintained via DCI size alignment and DCI size budget of DCI format 0_X/1_X is counted for each of the co-scheduled cells.
• Alt 1-2: DCI size budget is maintained via configured size for multi-cell scheduling DCI and DCI size budget of DCI format 0_X/1_X is counted for each of the co-scheduled cells.
• Alt 1-3: DCI size budget is maintained via DCI size alignment and DCI size budget of multi-cell scheduling DCI is counted only in one scheduled cell.
• Option 2: Existing DCI size budget is not necessarily maintained per scheduled cell.
• Alt 2-1: DCI size budget of multi-cell scheduling DCI is counted only in one scheduled cell.
• Alt 2-2: DCI size budget of multi-cell scheduling DCI is not counted per serving cell and not considered in the related serving cell specific DCI size alignment procedure, e.g., for K co-scheduled cells, gNB guarantee the total budget of 3*K DCI sizes is not exceeded.
• Alt 2-3: voiding the “3+1” limit for multi-cell scheduling
• Alt 2-4: the DCI size budget for DCI size alignment can be separately configured for each cell
• Alt 2-5: DCI size budget of the scheduling cell can be increased to account for the DCI format for multi-cell scheduling. Accordingly, the DCI size budget of a scheduled cell can be reduced.
• Other options/alternatives could be considered.

Agreement

Further study BD/CCE counting for multi-cell scheduling DCI based on below options:

• Alt 1: counted on each co-scheduled cell
• Alt 2: counted only in one scheduled cell
• Alt 3: scaled down to each of co-scheduled cell according to the number of co-scheduled cells
• Alt 4: counted as part of the scheduling cell instead of each scheduled cell
• Alt 5: scaled down to each of scheduled cells excluding scheduling cell
• Alt 6: counted on each co-scheduled cell excluding scheduling cell
• Other alternatives could be considered.

Agreement

For multi-cell scheduling, the co-scheduled cells are indicated by DCI format 0_X/1_X. At least the following options are considered:

·        Option 1: An indicator in the DCI points to one row of a table defining combinations of scheduled cells.

o   The table is configured by RRC signaling.

o   FFS: Separate tables can be configured for multi-cell PDSCH scheduling and multi-cell PUSCH scheduling.

·        Option 2: An indicator in the DCI is a bitmap corresponding to a set of configured cells that can be scheduled by the DCI 0_X/1_X

o   FFS: Separate sets of configured cells for multi-cell PDSCH scheduling and multi-cell PUSCH scheduling.

·        Option 3: using existing field (e.g., CIF, FDRA) to indicate whether one or more cells are scheduled or not

·        Other options are not precluded.

·        Note: It does not preclude other DCI information fields (e.g., BWP) to be jointly indicated by the indicator of the co-scheduled cells.

Decision: As per email decision posted on May 22^nd,

Agreement

For design of multi-cell scheduling DCI, companies are encouraged to consider following types of DCI fields:

·        Type-1 field: A single field indicating common information to all the co-scheduled cells or separate information to each of co-scheduled cells via joint indication or an information to only one of co-scheduled cells

·        Type-2 field: Separate field for each of the co-scheduled cells, or each sub-group comprising one or more co-scheduled cells where a single field is commonly applied to the co-scheduled cells belonging to a same sub-group

·        Type-3 field: Common or separate to each of the co-scheduled cells or to each sub-group.

o   FFS: whether it is dependent on explicit configuration or implicit condition (e.g., intra or inter band CA, FR1 or FR2).

·        Other types are not precluded.

Final summary in R1-2205488.

9.10.2     Multi-carrier UL Tx switching scheme

R1-2203665        Discussion on UL Tx switching across up to 3 or 4 bands     China Telecom

Proposal 1: RAN1 needs to clarify the UL CA cases involving SUL for Rel-18 UL Tx switching across up to 3 or 4 bands.

·          Whether both UL CA with one cell and multiple cells configured with SUL are the supported scenarios.

·          Whether both one SUL per band and multiple SUL per band are the supported scenarios.

Proposal 2: RAN1 needs to clarify whether UL transmission on a carrier without corresponding DL carrier implies to support UL carrier only cell without DL carrier.

Proposal 3: For Rel-18 UL Tx switching across up to 3 or 4 bands, the same state of Tx chain is applied to intra-band UL carriers in one band.

Proposal 4: For Rel-18 UL Tx switching across 3 bands each supporting maximum 2Tx chain, the mapping between UL transmission ports and Tx chain for inter-band UL CA Option 1 with and without SUL is defined as follows.

Proposal 5: For Rel-18 UL Tx switching across 4 bands each supporting maximum 2Tx chain, the mapping between UL transmission ports and Tx chain for inter-band UL CA Option 1 with and without SUL is defined as follows.

Proposal 6: For Rel-18 UL Tx switching across 3 bands each supporting maximum 2Tx chain, the mapping between UL transmission ports and Tx chain for inter-band UL CA Option 2 without SUL is defined as follows.

Proposal 7: For Rel-18 UL Tx switching across 4 bands each supporting maximum 2Tx chain, the mapping between UL transmission ports and Tx chain for inter-band UL CA Option 2 without SUL is defined as follows.

Proposal 8: For inter-band UL CA Option 1 with and without SUL, if Tx switching across 3 or 4 bands is configured, the switching period is only applicable when the UL transmissions are switched between different bands.

Proposal 9: For inter-band UL CA Option 2 without SUL, if Tx switching across 3 or 4 bands is configured, the switching period is applicable in the following cases:

·        If the current state of Tx chains is 2Tx on one band and 0Tx on other bands, the next UL transmission has a 2-port transmission on at least one carrier on one of other bands.

·        If the current state of Tx chains is 2Tx on one band and 0Tx on other bands, the next UL transmission has simultaneous 1-port transmission on two bands each on at least one carrier.

·        If the current state of Tx chains is 2Tx on one band and 0Tx on other bands, the next UL transmission only has a 1-port transmission on at least one carrier on one of other bands.

·        If the current state of Tx chains is 1Tx on one band and 1Tx on another band, the next UL transmission has a 2-port transmission on at least one carrier on a band.

·        If the current state of Tx chains is 1Tx on one band and 1Tx on another band, the next UL transmission has simultaneous 1-port transmission on two bands each on at least one carrier, at least one of the next transmitting two bands is different than the two current 1Tx bands.

·        If the current state of Tx chains is 1Tx on one band and 1Tx on another band, the next UL transmission only has a 1-port transmission on at least one carrier on a third band.

·        Proposal 10: Reuse the Rel-17 RRC configuration principle to address the issue that the state of Tx chains after Tx switching may not be unique.

Decision: The document is noted.

R1-2203136         Discussion on multi-carrier UL Tx switching              Huawei, HiSilicon

R1-2205131         Discussion on Multi-carrier UL Tx switching scheme ZTE        (rev of R1-2203208)

R1-2203347         Discussion on multi-carrier UL Tx switching scheme Spreadtrum Communications

R1-2205137         Discussion on multi-carrier UL Tx switching scheme CATT    (rev of R1-2203449)

R1-2203584         Discussion on UL TX switching     vivo

R1-2203743         Considerations on Multi-carrier UL Tx switching scheme        Sony

R1-2203801         Discussion on multi-carrier UL Tx switching scheme xiaomi

R1-2203926         Multi-carrier UL Tx switching scheme          Samsung

R1-2204027         Discussion on multi-carrier UL Tx switching scheme OPPO

R1-2204088         Multi-carrier UL Tx switching scheme          InterDigital, Inc.

R1-2204263         On the support of multi-carrier UL Tx switching scheme          Apple

R1-2204325         Discussion on multi-carrier UL Tx switching scheme CMCC

R1-2204399         Discussion on multi-carrier UL Tx switching scheme NTT DOCOMO, INC.

R1-2204632         Discussion on Multi-carrier UL Tx switching scheme LG Electronics

R1-2204724         On multi-carrier UL Tx switching scheme    MediaTek Inc.

R1-2204817         Discussions on multi-carrier UL Tx switching scheme              Intel Corporation

R1-2204889         Multi-carrier UL Tx switching        Ericsson

R1-2205052         Discussion on Rel-18 UL Tx switching         Qualcomm Incorporated

R1-2205089         Initial views on multi-carrier UL Tx switching scheme             Fujitsu Limited

R1-2205106         On Multi-Carrier UL Tx Switching Nokia, Nokia Shanghai Bell

//This one is to use NWM – please use RAN1-109-e-NWM-R18-MC_Enh-02 as the document name

[109-e-R18-MC_Enh-02] – Hiroki (NTT DOCOMO)

Email discussion on multi-cell UL Tx switching by May 20

-        Check points: May 12, May 18, May 20

R1-2205230        Summary of discussion on multi-carrier UL Tx switching scheme    Moderator (NTT DOCOMO, INC.)

From May 13^th GTW session

Conclusion

·        EN-DC cases are out of scope for Rel-18 UL Tx switching

Conclusion

·        UL only cell cases are out of scope for Rel-18 UL Tx switching

R1-2205363        Summary#2 of discussion on multi-carrier UL Tx switching scheme               Moderator (NTT DOCOMO, INC.)

Decision: As per email decision posted on May 18^th,

RAN1 observation

·        Four contributions (3136, 4724, 4909, 5131) from three companies show their evaluation results on UL Tx switching across 3 or 4 bands at RAN1#109-e meeting.

o   All evaluation results show the performance gain of UL Tx switching across 4 bands compared with UL Tx switching across 2 bands, assuming TDD bands with different TDD UL/DL configurations are included in 4 bands.

§  Evaluation results in 3136 show the performance gain of UL Tx switching across 4 bands compared with UL Tx switching across 3 bands.

§  Evaluation results in 4724 show that the performance gain of UL Tx switching across 4 bands compared with UL Tx switching across 2 bands depends on achievable switching period, and the longer switching period for UL Tx switching across 4 bands compared with UL Tx switching across 2 bands leads to reduction of the performance gain. Other evaluation results did not consider the impact of longer switching period for UL Tx switching across 4 bands compared with UL Tx switching across 2 bands.

§  Evaluation results in 5131 observe that the gain highly depends on the scheduling mechanism.

§  The range of performance gains shown in four contributions varies depending on the simulation assumptions.

Agreement

·        Companies are encouraged to investigate pros and cons of following possible mechanisms for dynamic Tx carrier switching across the configured bands, and RAN1 strives for the down-selection at RAN1#110

o   Alt.1: Dynamic Tx carrier switching can be across all the supported switching cases by the UE and based on the UL scheduling, i.e., via UL grant and/or RRC configuration for UL transmission

o   Alt.2: NW indicates 2 bands out of the configured bands (3 or 4 bands) via DCI or MAC-CE, and dynamic Tx carrier switching between indicated bands is same as Rel-17

o   Alt.3: One anchor band is selected among configured bands (3 or 4 bands), and dynamic Tx carrier switching can be performed only from the anchor band to a non-anchor band and from a non-anchor band to the anchor band

o   Note: Other mechanisms are not precluded

Agreement

·        Send LS to RAN4 to ask their feedback on the potential increase of switching period and complexity in the case of UL Tx switching across 3 or 4 bands

o   In the LS, observations based on the evaluation results and alternative switching mechanisms discussed in RAN1 are captured for the information to RAN4

o   In the LS, RAN1 also asks RAN4 feedback on whether following assumption can be considered as baseline UE assumption/behavior even in case of the UL Tx switching across 3 or 4 bands

§  When one of the two Tx chains is triggered to switch from one band to another band, another Tx chain which is in any of bands is also not expected to be used for transmission during the switching period

R1-2205363         Summary#2 of discussion on multi-carrier UL Tx switching scheme      Moderator (NTT DOCOMO, INC.)

R1-2205471        Summary#3 of discussion on multi-carrier UL Tx switching scheme               Moderator (NTT DOCOMO, INC.)

From May 19^th GTW session

Conclusion

·        If Rel-18 UL Tx switching is supported, following assumption is applied for Rel-18 UL Tx switching across up to 3 or 4 bands

o   Only when the two Tx chains are linked to one NR band, the 2-ports UL transmission on the NR band is possible

RAN1 Observation

Following proposals to address the concern on UE/gNB complexity increase or scheduling restriction due to UL Tx switching across larger number of bands compared with Rel-16/17 are identified in contributions submitted at RAN1#109-e, and companies are encouraged to investigate pros and cons of the proposals so that one or some of them may be down-selected after the down-selection of the mechanism for dynamic Tx carrier switching across the configured bands

·        UE can report the supports of only some of concurrent UL cases (combinations of 2 bands for concurrent UL transmissions)

·        Switching across 0/1/2 ports is supported only for 2 configured bands out of 3 or 4 configured bands and other bands support switching across 0/1 port only

·        Only switching across 0/1 port is supported across all configured bands when 3 or 4 bands are configured

·        Prioritization rules between uplink carriers are specified

·        No restriction on the UEs choice of MIMO capability on any of the bands/CCs involved in the UL Tx switching band combination is introduced

·        After one RF state switch, the next RF state switch must occur after 14 symbols or later (FFS: which SCS is assumed for the symbol duration)

·        Note: Other solutions are not precluded

·        Note: each proposal assumes certain mechanism for dynamic Tx carrier switching across the configured bands, and hence some or all of the proposals may not be necessary depending on the down selection of the mechanism for dynamic Tx carrier switching across the configured bands

Conclusion

It is RAN1’s understanding that RAN4 should lead the discussion on UL Tx switching with multiple TAGs for both 2 bands case and more than 2 bands case

·        For further discussion in RAN1 with regards to UL Tx switching with multiple TAGs, it will be discussed only if triggered by RAN4

·        If it is decided to support UL Tx switching with multiple TAGs, it is RAN1's working assumption that the number of TAGs should be limited to up to 2

RAN1 Observation

Following possible switching configurations can be considered, and RAN1 may discuss if any of the following switching configurations need to be supported after making some progress on the discussion on the switching mechanism

·        For 3 bands case

o   Switching configuration.3-1: all the 3 bands support up to 2Tx

o   Switching configuration.3-2: only 1 band out of 3 bands support up to 2Tx

o   Switching configuration.3-3: only 2 bands out of 3 bands support up to 2Tx

·        For 4 bands case

o   Switching configuration.4-1: all the 4 bands support up to 2Tx

o   Switching configuration.4-2: only 1 band out of 4 bands support up to 2Tx

o   Switching configuration.4-3: only 2 bands out of 4 bands support up to 2Tx

o   Switching configuration.4-4: only 3 bands out of 4 bands support up to 2Tx

·        Note: separate switching configuration for switched UL and dual UL is not precluded

·        Note: In addition to the UE/gNB complexity reduction, performance reduction caused by any scheduling restriction can also be taken into account

·        Note: The Spec should not restrict which Tx chain is fixed or switched across certain bands.

R1-2205501        [Draft] LS on UL Tx switching across 3 or 4 bands in Rel-18            Moderator (NTT DOCOMO)

Decision: The draft LS is endorsed. Approved in R1-2205502.

R1-2205589        Summary#4 of discussion on multi-carrier UL Tx switching scheme               Moderator (NTT DOCOMO, INC.)

9.10.33     Other

R1-2203209         Simulation evaluation on Rel-18 Multi-carrier enhancement    ZTE

R1-2204890         Other aspects related to multi-carrier enhancements   Ericsson

R1-2204909         Simulation evaluations of single user experience data rate for multi-carrier UL Tx switching             Huawei, HiSilicon

 RAN1#110

9.10   Multi-carrier enhancements for NR

Please refer to RP-221435 for detailed scope of the WI.

[110-R18-MC_Enh] Email to be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc – Hiroki (DOCOMO)

9.10.1     Multi-cell PUSCH/PDSCH scheduling with a single DCI

R1-2205862         Discussion on multi-cell scheduling with a single DCI              Huawei, HiSilicon

R1-2205962         Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI               ZTE

R1-2206059         Discussion on multi-cell scheduling vivo

R1-2206103         Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI               Langbo

R1-2206155         On multi-cell PUSCH/PDSCH scheduling with a single DCI    Nokia, Nokia Shanghai Bell

R1-2206176         Consideration on multi-cell PUSCH/PDSCH scheduling with a single DCI               Fujitsu

R1-2206326         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI OPPO

R1-2206382         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI CATT

R1-2206451         Discussion on multi-cell scheduling via a single DCI  Lenovo

R1-2206467         Discussion on Multi-cell PXSCH scheduling with a single DCI              NEC

R1-2206599         Discussions on multi-cell scheduling with a single DCI             Intel Corporation

R1-2206627         Discussion on the design of multi-cell scheduling with a single DCI       Xiaomi

R1-2206663         Multi-cell scheduling with a single DCI        InterDigital, Inc.

R1-2206682         Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI               CAICT

R1-2206700         Discussion on multi-cell scheduling with a single DCI              China Telecom

R1-2206844         Multi-cell PUSCH/PDSCH scheduling with a single DCI         Samsung

R1-2206929         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI CMCC

R1-2207007         On multi-cell PUSCH/PDSCH scheduling with a single DCI    MediaTek Inc.

R1-2207040         Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI               LG Electronics

R1-2207097         Discussion on Multicarrier scheduling with a single DCI          FGI

R1-2207143         Discussions on multi-cell scheduling with a single DCI             Sharp

R1-2207251         Multi-cell PUSCH/PDSCH scheduling with a single DCI         Qualcomm Incorporated

R1-2207349         On multi-cell PUSCH/PDSCH scheduling with a single DCI    Apple

R1-2207424         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI NTT DOCOMO, INC.

R1-2207441         Multi-cell PUSCH/PDSCH scheduling with a single DCI         Ericsson

R1-2207447         Discussion on multi-cell scheduling with a single DCI              ITRI

R1-2207553         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI Google Inc.

R1-2207695         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI Spreadtrum Communications (rev of R1-2206005)

R1-2207769        Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI       Moderator (Lenovo)

From Monday session

Agreement

All the co-scheduled cells by a DCI format 0_X and the scheduling cell are included in the same PUCCH group.

Agreement

·        Confirm below working assumption reached in RAN1#109e meeting.

o   (Working assumption) DCI format 0_X/1_X is a new DCI format for multi-cell scheduling

R1-2207770        Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI       Moderator (Lenovo)

From Tuesday session

Working assumption:

For a cell within a set of cells which can be co-scheduled by a DCI format 0_X/1_X, support monitoring the DCI format 0_X/1_X and legacy single cell scheduling DCI format(s) from a same scheduling cell.

·        The DCI format 0_X/1_X and the legacy DCI format(s) can be monitored simultaneously.

·        FFS: whether monitoring of the DCI format 0_X/1_X and the legacy DCI format(s) is supported for one, a subset, or all cells within the set of cells.

·        FFS: number of different DCI sizes for 0_X/1_X and for legacy DCI formats

·        FFS: whether to support a subset or all legacy DCI format(s) to be monitored with DCI 0_X/1_X

Working assumption:

·        The maximum number of co-scheduled cells by a DCI format 1_X in Rel-18 is 4.

·        The maximum number of co-scheduled cells by a DCI format 0_X in Rel-18 is 4.

FFS: The maximum number of configurable cells for co-scheduling

R1-2207771        Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI       Moderator (Lenovo)

R1-2208046        Feature lead summary#4 on multi-cell PUSCH/PDSCH scheduling with a single DCI       Moderator (Lenovo)

From Friday session

Agreement

For discussing field design of DCI format 0_X/1_X which schedules more than one cell, reformulate the types of DCI fields as below:

• Type-1 field:
• Type-1A field: A single field indicating common information to all the co-scheduled cells
• Type-1B field: A single field indicating separate information to each of co-scheduled cells via joint indication
• Type-1C field: A single field indicating an information to only one of co-scheduled cells
• Type-2 field: Separate field for each of the co-scheduled cells
• Type-3 field: Common or separate to each of the co-scheduled cells, or separate to each sub-group, dependent on explicit configuration.
• Note: One sub-group comprises a subset of co-scheduled cells where a single field is commonly applied to the co-scheduled cell(s) belonging to a same sub-group.
• Note: Handling of any parameters applicable to multi-cell scheduling where corresponding fields are not included in DCI format 0_X/1_X (if any) will be separately discussed.

Agreement

For DCI format 1_X/0_X which can schedule more than one cell,

• Type-1 fields at least include below:
• Type-1A:
• Identifier for DCI formats
• Downlink assignment index
• TPC for scheduled PUCCH
• PUCCH resource indicator
• PDSCH-to-HARQ timing indicator
• One-shot HARQ-ACK request
• Type-2 fields at least include below:
• New data indicator per TB
• Redundancy version per TB
• FFS: Other fields to be included in DCI format 1_X/0_X and which type of the fields belongs to.
• FFS: size for each field

Agreement

When UE detects a DCI format 1_X scheduling a set of PDSCHs, the UE provides corresponding HARQ-ACK information in a PUCCH transmission within UL slot , where  is a number of slots and is indicated by the PDSCH-to-HARQ_feedback timing indicator field in the DCI format and  is the last UL slot overlapping with the DL slot  for the reference PDSCH reception for slot-based PUCCH or an UL slot overlapping with the end of the reference PDSCH reception in DL slot  for sub-slot based PUCCH.

·        FFS details of reference PDSCH

Agreement

• For Type-2 HARQ-ACK codebook, two sub-codebooks are generated with a first sub-codebook comprising HARQ-ACK information bits for PDSCH(s) scheduled by DCI(s) with each scheduling a single cell and a second sub-codebook comprising HARQ-ACK information bits for PDSCH(s) scheduled by DCI(s) with each scheduling more than one cell.
• Separate DAI counting for DCI(s) with each scheduling a single cell and DCI(s) with each scheduling more than one cell.
• FFS whether a DCI scheduling more than one cell is associated with the first sub-codebook or the second sub-codebook when the number of cells with actual PDSCH reception due to collision with semi-static TDD DL/UL configuration is one.
• Type-2 HARQ-ACK codebook is generated by concatenating the first sub-codebook and the second sub-codebook.
• If at least one cell of the set of cells which can be co-scheduled by a DCI format 1_X is configured with maximum 2 codewords per PDSCH without spatial bundling,
• FFS: the number of HARQ-ACK information bits for each DCI format 1_X that schedules more than one cell;
• Otherwise, the number of HARQ-ACK information bits for each DCI format 1_X that schedules more than one cell is equal to N, where N is the maximum number of cells which can be co-scheduled by a DCI format 1_X in the PUCCH group for the UE.
• HARQ-ACK information bits for co-scheduled PDSCHs by a DCI format 1_X is ordered based on serving cell indices associated with co-scheduled PDSCHs.
• HARQ-ACK bundling across co-scheduled cells is not supported for multi-cell scheduling.

Agreement

UE does not expect to be configured both CBG-based PDSCH/PUSCH transmission and the multi-cell PDSCH/PUSCH scheduling on the same or different cells within a same PUCCH group.

Agreement

• At least cases 1-1 and 1-2 on SCS are supported:
• Case 1-1: A DCI format 0-X/1-X on a scheduling cell can schedule multiple cells including the scheduling cell and same SCS is used among all the co-scheduled cells including the scheduling cell.
• Case 1-2: A DCI format 0-X/1-X on a scheduling cell can schedule multiple cells not including the scheduling cell and same SCS is used among all the co-scheduled cells which may be same or different to the SCS of the scheduling cell.
• Case 1-3: A DCI format 0-X/1-X on a scheduling cell can schedule multiple cells including the scheduling cell and different SCS is used among the co-scheduled cells including the scheduling cell.
• Case 1-4: A DCI format 0-X/1-X on a scheduling cell can schedule multiple cells not including the scheduling cell and different SCS is used among the co-scheduled cells.
• FFS: Whether Case 1-3 or 1-4 is additionally supported.

Final summary in R1-2208048        (rev of R1-2208047).

9.10.22     Multi-carrier UL Tx switching scheme

R1-2205863         Discussion on multi-carrier UL Tx switching              Huawei, HiSilicon

R1-2205963         Discussion on Multi-carrier UL Tx switching scheme ZTE

R1-2206006         Discussion on multi-carrier UL Tx switching scheme Spreadtrum Communications

R1-2206060         Discussion on UL TX switching     vivo

R1-2206130         Considerations on Multi-carrier UL Tx switching scheme        Sony

R1-2206177         Views on multi-carrier UL Tx switching scheme        Fujitsu

R1-2206327         Discussion on multi-carrier UL Tx switching scheme OPPO

R1-2206383         Discussion on multi-carrier UL Tx switching scheme CATT

R1-2206434         On Multi-Carrier UL Tx Switching Nokia, Nokia Shanghai Bell

R1-2206600         Discussions on multi-carrier UL Tx switching scheme              Intel Corporation

R1-2206628         Discussion on multi-carrier UL Tx switching scheme Xiaomi

R1-2206664         Multi-carrier UL Tx switching scheme          InterDigital, Inc.

R1-2206701         Discussion on UL Tx switching across up to 3 or 4 bands         China Telecom

R1-2206845         On multi-carrier UL Tx switching   Samsung

R1-2206930         Discussion on multi-carrier UL Tx switching scheme CMCC

R1-2206986         On multi-carrier UL Tx switching scheme    MediaTek Inc.

R1-2207041         Discussion on Multi-carrier UL Tx switching scheme LG Electronics

R1-2207252         Discussion on Rel-18 UL Tx switching         Qualcomm Incorporated

R1-2207350         On multi-carrier UL Tx switching   Apple

R1-2207425         Discussion on multi-carrier UL Tx switching scheme NTT DOCOMO, INC.

R1-2207442         Multi-carrier UL Tx switching        Ericsson

R1-2207555         Discussion on multi-carrier UL Tx switching scheme Google Inc.

R1-2207752         Summary on discussion on multi-carrier UL Tx switching scheme         Moderator (NTT DOCOMO, INC.)

R1-2207870        Summary#2 on discussion on multi-carrier UL Tx switching scheme               Moderator (NTT DOCOMO, INC.)

R1-2207942        Summary#3 on discussion on multi-carrier UL Tx switching scheme               Moderator (NTT DOCOMO, INC.)

From Wed session

Working Assumption

• If Rel-18 UL Tx switching is supported, following switching mechanism is considered as baseline for the Rel-18 UL Tx switching across 3 or 4 bands
• Alt.1: Dynamic Tx carrier switching can be across all the supported switching cases by the UE and based on the UL scheduling, i.e., via dynamic grant and/or RRC configuration for UL transmission
• RAN1 will support one or more of following complexity reduction options, considering at least the potential additional preparation time, additional interruption time, and RF complexity for certain switching cases/patterns, if Rel-18 UL Tx switching is supported based on Alt.1, and companies are encouraged to investigate options with striving for down-selection at RAN1#110bis-e.
• Option 1: UE is allowed to support only some of concurrent UL cases (band pairs)
• FFS: at least one band pair should be supported as in Rel-17
• FFS: for both 3 and 4 bands cases or only for 4 bands case
• FFS: potential capability/RRC signaling
• Option 2: UE is allowed to support 2 ports transmission only on some of bands out of configured bands for UL Tx switching
• FFS: at least two bands should support up to 2 Tx as in Rel-17
• FFS: for both 3 and 4 bands cases or only for 4 bands case
• FFS: for both switched UL and dual UL cases or only for dual UL case
• FFS: whether/how to reuse or extend existing capability/RRC signaling
• Option 3: UE is allowed with more preparation procedure time (or interruption time) only for some specific switching cases/patterns
• FFS: specific switching cases/patterns where more preparation procedure time (or interruption time) is necessary, e.g., switching patterns not existed in Rel-17
• FFS: how long preparation procedure time and/or interruption time is necessary, and whether RAN4 involvement is necessary
• FFS: whether/how to report/indicate the specific switching cases/patterns and/or value(s) of preparation procedure time (or interruption time)
• FFS: what is the definition of preparation procedure time or interruption time, including whether interruption happens during the preparation procedure time and whether it includes switching period
• FFS: whether/how long minimum interval between two succeeding UL Tx switching is necessary
• Option 4: UE is allowed to support only some of band pairs for tx switching
• FFS: at least one band pair should be supported as in Rel-17
• FFS: for both 3 and 4 bands cases or only for 4 bands case
• FFS: for switched UL and/or dual UL
• FFS: potential capability/RRC signaling
• Other options are not precluded

 RAN1#110-bis-e

9.9       Multi-carrier enhancements for NR

Please refer to RP-222251 for detailed scope of the WI.

9.9.1        Multi-cell PUSCH/PDSCH scheduling with a single DCI

R1-2208426         Discussion on multi-cell scheduling with a single DCI              Huawei, HiSilicon

R1-2208486         Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI               ZTE

R1-2208564         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI Spreadtrum Communications

R1-2208658         Discussion on multi-cell scheduling vivo

R1-2208779         Discussion on multi-cell scheduling with a single DCI              China Telecom

R1-2208860         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI OPPO

R1-2208991         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI CATT

R1-2208997         Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI               Langbo

R1-2209020         Consideration on multi-cell PUSCH/PDSCH scheduling with a single DCI               Fujitsu

R1-2209067         Discussions on multi-cell scheduling with a single DCI             Intel Corporation

R1-2209239         Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI               CAICT

R1-2209299         Discussion on the design of multi-cell scheduling with a single DCI       xiaomi

R1-2209305         On multi-cell scheduling via a single DCI     Lenovo

R1-2209352         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI CMCC

R1-2209416         Discussion on Multicarrier scheduling with a single DCI          FGI

R1-2209426         Discussion on Multi-cell PXSCH scheduling with a single DCI              NEC

R1-2209454         Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI               LG Electronics

R1-2209516         On multi-cell PUSCH/PDSCH scheduling with a single DCI    MediaTek Inc.

R1-2209595         On multi-cell PUSCH/PDSCH scheduling with a single DCI    Apple

R1-2209746         On multi-cell PUSCH/PDSCH scheduling with a single DCI    Samsung

R1-2209860         Multi-cell PUSCH/PDSCH scheduling with a single DCI         Ericsson

R1-2209917         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI NTT DOCOMO, INC.

R1-2210000         Multi-cell PUSCH/PDSCH scheduling with a single DCI         Qualcomm Incorporated

R1-2210032         Discussion on multi-cell scheduling with a single DCI              ITRI

R1-2210034         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI Google Inc.

R1-2210151         On multi-cell PUSCH/PDSCH scheduling with a single DCI    Nokia, Nokia Shanghai Bell

[110bis-e-R18-MC_Enh-01] – Haipeng (Lenovo)

Email discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI by October 19

-        Check points: October 14, October 19

R1-2210350        Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI       Moderator (Lenovo)

From Oct 12th GTW session

Agreement:

·        Confirm below working assumption reached in RAN1#110 meeting.

Working Assumption

§  The maximum number of co-scheduled cells by a DCI format 1_X in Rel-18 is 4.

§  The maximum number of co-scheduled cells by a DCI format 0_X in Rel-18 is 4.

§  FFS: The maximum number of configurable cells for co-scheduling

Agreement:

At least below fields are excluded from DCI format 1_X/0_X:

·        CBGTI

·        CBGFI

·        PDSCH group index

·        New feedback indicator

·        Number of requested PDSCH group(s)

·        Sidelink assignment index

·        Second TPC command for scheduled PUSCH

·        Second SRS resource indicator

·        Second Precoding information

·        Second PTRS-DMRS association

·        Second TPC command for scheduled PUCCH

Agreement:

For DCI format 1_X/0_X, Type-1 fields at least include below:

·        Priority indicator

·        Indicator of co-scheduled cells

·        beta offset indicator

·        CSI request

·        UL-SCH indicator

·        FFS: ChannelAccess-CPext

R1-2210351        Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI       Moderator (Lenovo)

From Oct 14th GTW session

Agreement:

Confirm below working assumption reached in RAN1#110 meeting with revision.

Working Assumption

•        For any cell within a set of cells which can be co-scheduled by a DCI format 0_X/1_X, RAN1 specification supports monitoring the DCI format 0_X/1_X and DCI format 0_0/1_0, 0_1/1_1, and/or 0_2/1_2 (if supported by the UE), if configured from a same scheduling cell.

o   The DCI format 0_X/1_X and the DCI format 0_0/1_0/0_1/1_1/0_2/1_2 can be monitored simultaneously.

o   Note: This does not mean a UE is required to support number of BDs/CCEs beyond the Rel-17 limits (i.e.,  and ) for PDCCH candidates for each scheduled cell.

Decision: As per email decision posted on Oct 15th,

Agreement

For a set of cells co-scheduled by a DCI format 0_X/1_X, time domain resource allocations for the set of cells are jointly indicated by a single TDRA field in the DCI format 0_X/1_X.

•         Separate {SLIV, mapping type, scheduling offset K0 (or K2)} is indicated for each of co-scheduled PDSCHs/PUSCHs.

•         FFS details of the TDRA table design

Agreement

Confirm below working assumption:

Working Assumption

HARQ-ACK codebook types (Type-1, Rel-15 Type-2, Rel-16 Type-3, Rel-17 Type-3) are applicable when multi-cell PDSCH scheduling is configured.

R1-2210352        Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI       Moderator (Lenovo)

From Oct 19th GTW session

Working Assumption

For a set of cells which is configured for multi-cell scheduling,

•        Existing DCI size budget is maintained on each cell of the set of cells.

•        DCI size of DCI format 0_X/1_X is counted on one cell among the set of cells.

o   FFS which cell DCI size of the DCI format 0_X/1_X is counted on.

•        BD/CCE of DCI format 0_X/1_X is counted on one cell among the set of cells.

o   FFS which cell BD/CCE of the DCI format 0_X/1_X is counted on.

•        Search space of DCI format 0_X/1_X is configured on one cell of the set of cells and associated with the search space of the scheduling cell with the same search space ID.

o   FFS which cell the SS of the DCI format 0_X/1_X is configured on.

•        FFS: How to address Rel-17 BD/CCE limit for any given cell (operating the feature under Rel-17 BD/CCE limit)

•        Note: This does not mean a UE is required to support number of BDs/CCEs beyond the Rel-17 limits (i.e.,  and ) for PDCCH candidates for each scheduled cell.

Decision: As per email decision posted on Oct 20th,

Agreement

•        UE does not expect to be configured both multi-PDSCH scheduling and multi-cell PDSCH scheduling on the same or different cells within a same PUCCH group.

Agreement

•        For Type-2 HARQ-ACK codebook, if at least one cell of a set of cells which can be co-scheduled by DCI format 1_X is configured with maximum 2 codewords per PDSCH without spatial bundling, the number of HARQ-ACK information bits for each DCI format 1_X that schedules more than one cell of the set of cells is equal to M, where M is the maximum number of TBs which can be co-scheduled by a DCI format 1_X in the PUCCH group for the UE.

Agreement

•        For Type-2 HARQ-ACK codebook, a DCI format 1_X scheduling more than one cell is associated with the second sub-codebook when the number of cells with actual PDSCH reception due to collision with semi-static TDD DL/UL configuration is one.

•        If a UE is scheduled by a DCI format 1_X to receive PDSCH over multiple cells, and if tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated, indicates that, for a cell from the multiple cells, at least one symbol from a set of symbols where the UE is scheduled PDSCH reception in the cell is an uplink symbol, the UE does not receive the PDSCH in the cell.

•        If a UE is scheduled by a DCI format 0_X to transmit PUSCH over multiple cells, and if tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated, indicates that, for a cell from the multiple cells, at least one symbol from a set of symbols where the UE is scheduled PUSCH transmission in the cell is a downlink symbol, the UE does not transmit the PUSCH in the cell.

Final summary in R1-2210662.

9.9.22        Multi-carrier UL Tx switching scheme

R1-2208427         Discussion on multi-carrier UL Tx switching              Huawei, HiSilicon

R1-2208487         Discussion on Multi-carrier UL Tx switching scheme ZTE

R1-2208565         Discussion on multi-carrier UL Tx switching scheme Spreadtrum Communications

R1-2208659         Discussion on UL TX switching     vivo

R1-2208780         Discussion on UL Tx switching across up to 3 or 4 bands         China Telecom

R1-2208861         Discussion on multi-carrier UL Tx switching scheme OPPO

R1-2208992         Discussion on multi-carrier UL Tx switching scheme CATT

R1-2209068         Discussions on multi-carrier UL Tx switching scheme              Intel Corporation

R1-2209300         Discussion on multi-carrier UL Tx switching scheme xiaomi

R1-2209353         Discussion on multi-carrier UL Tx switching scheme CMCC

R1-2209455         Discussion on Multi-carrier UL Tx switching scheme LG Electronics

R1-2209596         On multi-carrier UL Tx switching   Apple

R1-2209747         On multi-carrier UL Tx switching   Samsung

R1-2209772         On multi-carrier UL Tx switching scheme    MediaTek Inc.

R1-2209861         Multi-carrier UL Tx switching        Ericsson

R1-2209918         Discussion on Multi-carrier UL Tx switching scheme NTT DOCOMO, INC.

R1-2210001         Discussion on Rel-18 UL Tx switching         Qualcomm Incorporated

R1-2210035         Discussion on multi-carrier UL Tx switching scheme Google Inc.

R1-2210192         On Multi-Carrier UL Tx Switching Nokia, Nokia Shanghai Bell

[110bis-e-R18-MC_Enh-02] – Hiroki (NTT DOCOMO)

Email discussion on multi-carrier UL TX switching scheme by October 19

-        Check points: October 14, October 19

R1-2210280        Summary#1 of discussion on multi-carrier UL Tx switching scheme               Moderator (NTT DOCOMO, INC.)

From Oct 12th GTW session

Agreement:

If Rel-18 UL Tx switching for 3 or 4 bands with dual UL is supported, UE is allowed to support only some of band pairs for concurrent UL transmission based on UE capability

·        The supported band pair for concurrent transmission requires the support of UL CA on the corresponding band pair(s) by the UE

·        Details on the UE capability such as how to report the support of dual UL and the supported band pair(s) for concurrent UL transmission are further discussed

·        Details on the gNB configuration/indication such as how to indicate the band pair(s) UE should expect for concurrent UL transmission are further discussed

·        Note: UE is also allowed to support all band pairs for concurrent transmission, and the design of Rel-18 UL Tx switching for 3 or 4 bands with dual UL does not impose any restriction

Agreement:

If Rel-18 UL Tx switching for 3 or 4 bands is supported, UE is allowed to support only some of band(s) for up to 2 ports UL transmission based on UE capability

·        Further down-select from the following alternatives

o   Alt.1: no restriction for both switched UL and dual UL and for both 3 bands and 4 bands

o   Alt.2: at least one band should support up to 2 ports UL transmission for both switched UL and dual UL and for both 3 bands and 4 bands

o   Alt.3: at least two bands should support up to 2 ports UL transmission for both switched UL and dual UL and for both 3 bands and 4 bands

·        Details on the UE capability such as whether existing per-FS UL-MIMO capability can be reused or not are further discussed

·        Details on the gNB configuration/indication such as whether/how to additionally indicate 2 ports UL transmission mode for a band/cell are further discussed

·        Existing MIMO mechanism for MIMO mode indication should be reused

·        Note: UE is also allowed to support all bands for up to 2 ports UL transmission, and the design of Rel-18 UL Tx switching for 3 or 4 bands does not impose any restriction

Agreement:

If Rel-18 UL Tx switching for 3 or 4 bands is supported, following is considered as baseline.

·        Existing conditions where the switching period is required can be reused for Rel-18 UL Tx switching with 3 or 4 bands when only two bands are involved in a switching

·        New conditions where the switching period is required should be introduced for Rel-18 UL Tx switching with 3 or 4 bands when more than two bands are involved in a switching

o   For dual UL, following new conditions are considered

§  When the UE is to transmit a 1-port or 2-port transmission on one uplink carrier on one band (1^st band) and if Tx chain state at the preceding uplink transmission is 1T + 1T each on a carrier on other different bands (2^nd and 3^rd band)

§  When the UE is to transmit a 1-port + 1-port transmission each on one uplink carrier on different bands (1^st and 2^nd band) and if Tx chain state at the preceding uplink transmission is 2T on a carrier on another band (3^rd band)

§  When the UE is to transmit a 1-port + 1-port transmission each on one uplink carrier on different bands (1^st and 2^nd band) and if Tx chain state at the preceding uplink transmission is 1T + 1T each on a carrier on one of the bands and another different band (1^st or 2^nd band, and 3^rd band)

§  When the UE is to transmit a 1-port + 1-port transmission each on one uplink carrier on different bands (1^st and 2^nd band) and if Tx chain state at the preceding uplink transmission is 1T + 1T each on a carrier on other different bands (3^rd and 4^th band)

o   FFS for switched UL and/or for the case with complexity reduction option 1 or 2

o   FFS the same or different switch period for existing conditions and new conditions

R1-2210455        Summary#2 of discussion on multi-carrier UL Tx switching scheme               Moderator (NTT DOCOMO, INC.)

From Oct 14th GTW session

Conclusion

No consensus in RAN1 on complexity reduction option 3.

Decision: As per email decision posted on Oct 15th,

Agreement

• Consider following alternatives for UE capability reporting about the supported UL Tx switching options
• Alt.1: report {switchedUL, dualUL, both} for each band pair in the band combination
• Alt.2: report {switchedUL, dualUL, both} for the band combination and report supported band pair for concurrent transmission for the band combination
• Consider following alternatives for gNB configuration regarding dual UL
• Alt.1: configure {switchedUL, dualUL} in CellGroupConfig
• Alt.2: configure {switchedUL, dualUL} for each band pair (combination of serving cells?)
• Alt.3: at least configuration of supported band pair (combination of serving cells) for concurrent transmission
• Alt.4: No configuration of supported band pair (combination of serving cells) for concurrent transmission, i.e., UE just assumes as it reports

Working Assumption

Specify UL Tx switching schemes across up to 4 bands in Rel-18.

Working Assumption

If Rel-18 UL Tx switching for 3 or 4 bands is supported, both Switched UL and Dual UL are supported.

R1-2210548         Summary#3 of discussion on multi-carrier UL Tx switching scheme      Moderator (NTT DOCOMO, INC.)

Decision: As per email decision posted on Oct 18th,

Agreement

Confirm the following working assumption made at the RAN1#110 meeting.

Working Assumption

If Rel-18 UL Tx switching is supported, following switching mechanism is considered as baseline for the Rel-18 UL Tx switching across 3 or 4 bands

·        Alt.1: Dynamic Tx carrier switching can be across all the supported switching cases by the UE and based on the UL scheduling, i.e., via dynamic grant and/or RRC configuration for UL transmission

Working Assumption

At least for dual UL, reuse existing RRC parameter {oneT, twoT} via uplinkTxSwitching-DualUL-TxState to solve the issue on ambiguous switching state at least for following cases

• Case#1 of the issue: two Tx chains are currently associated with band A, and next transmission is 1 port transmission on band B, but there are multiple possible switching cases where 1P on band B is supported
• if twoT is indicated, both of two Tx chains are switched to band B
• if oneT is indicated, one Tx chain is switched to band B while another Tx chain remains on band A
• Case#2 of the issue: two Tx chains are currently associated with band A and B, and next transmission is 1 port transmission on band C, but there are multiple possible switching cases where 1P on band C is supported
• if twoT is indicated, both of two Tx chains are switched to band C
• if oneT is indicated, one Tx chain is switched to band C while how to determine the associated band for another Tx chain is FFS
• Alt.1: based on gNB’s configuration/indication e.g., new RRC parameter
• Alt.2: based on predefined rule
• Other alternative is not precluded
• FFS for other potential cases

Decision: As per email decision posted on Oct 19th,

Agreement

Ask RAN2 to consider following alternatives for UE capability reporting about the supported UL Tx switching options

·        Alt.1: report {switchedUL, dualUL, both} for each band pair in the band combination

·        Alt.2: report {switchedUL, dualUL, both} for the band combination and report supported band pair for concurrent transmission for the band combination

o   Note：If there is no report on the supported band pair(s) for concurrent transmission while the UE reports “dualUL” or “both” for the band combination, gNB may assume that the UE supports concurrent transmission on all the band pairs within the band combination

·        Alt.3: report {dualUL} for each band pair in the band combination

o   Note: Within the band combination, the UE shall be capable of being operated in switched UL mode for all band pairs

Agreement

Ask RAN2 to consider following alternatives and specify gNB configuration

·        Alt.1: configure {switchedUL, dualUL} for all serving cells (i.e., for the band combination)

·        Alt.2: configure {switchedUL, dualUL} for combination(s) of serving cells (i.e., for each band pair in the band combination)

·        Alt.3: configure {switchedUL, dualUL} for all serving cells (i.e., for the band combination), and configure combination(s) of serving cells (i.e., as supported serving cell pair(s) for each band pair in the band combination) for concurrent transmission

Working assumption

Study the following alternatives for the minimum separation time between two UL Tx switchings for Rel-18 UL Tx switching schemes across up to 3 or 4 bands, and decide in RAN1#111 whether/which of the following alternatives is needed

·        Alt.1: define 14 symbols based on a SCS (FFS on SCS) as minimum separation time between two UL Tx switchings

·        Alt.2: define that no more than one uplink Tx switching within a reference slot based on a SCS (FFS on SCS)

·        Alt.3: define X slots as minimum separation time between two UL Tx switchings where 3 bands are involved in total, and define Y slots as minimum separation time between two UL Tx switchings where 4 bands are involved in total, where X and/or Y is no less than 1 (FFS on X,Y, FFS reference SCS for the slots in case of multiple SCSs across carriers or expressed in unit of micro second)

·        Alt.4: report the minimum separation time for different switching cases

·        Other alternative is not precluded

·        FFS: Applicable cases for the restriction

·        Note: Companies are encouraged to provide detailed numbers of minimum separation time

Agreement

Consider following alternatives on the supported switching cases (Tx chain states) for each scenario

• Scenario#1: For switched UL, if UE supports up to 2 ports UL transmission on all the bands in the band combination,
• Alt.1-1: only switching cases (Tx chain states) with 2T are assumed
• In case of 3 bands, 3 switching cases ({2T,0T,0T}, {0T,2T,0T}, {0T,0T,2T}) are assumed
• In case of 4 bands, 4 switching cases ({2T,0T,0T,0T}, {0T,2T,0T,0T}, {0T,0T,2T,0T}, {0T,0T,0T,2T}) are assumed
• Alt.1-2: switching cases (Tx chain states) with 1T-1T can also be assumed
• FFS: detailed switching cases to be assumed
• Scenario#2: For switched UL, if UE supports up to 2 ports UL transmission only on some of the bands,
• Alt.2-1: for the band where 2 ports UL transmission is not supported, switching cases (Tx chain states) with 1T-1T can be assumed
• FFS: detailed switching cases to be assumed with different number of bands supporting up to 2 ports UL transmission
• Alt.2-2: only switching cases (Tx chain states) with 2T are assumed
• Assumed switching cases are same as Scenario#1
• Alt.2-3: switching cases (Tx chain states) with 1T-1T can also be assumed
• FFS: detailed switching cases to be assumed
• FFS: Scenario#3: For dual UL, if UE does not support concurrent transmission on specific band pair(s) and supports up to 2 ports UL transmission on all the bands in the band combination,
• Alt.3-1: corresponding switching case(s) with 1T-1T for the band pair(s) are not assumed
• FFS: if UE does not support concurrent transmission on specific band pair(s) and supports up to 2 ports UL transmission only on some of the bands
• Alt.3-2: corresponding switching case(s) with 1T-1T for the band pair(s) are assumed
• Assumed switching cases are same as the case where UE supports dual UL for all band pairs in the band combination

R1-2210724        LS on UE capability and gNB configuration for UL Tx switching across 3 or 4 bands in Rel-18  RAN1, NTT DOCOMO

Decision: As per email decision posted on Oct 19th, the LS is approved.

Final summary in R1-2210723.

 RAN1#111

9.9       Multi-carrier enhancements for NR

Please refer to RP-222251 for detailed scope of the WI.

[111-R18-MC_Enh] – Hiroki (NTT DOCOMO)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

9.9.1        Multi-cell PUSCH/PDSCH scheduling with a single DCI

R1-2210856         Discussion on multi-cell scheduling with a single DCI              Huawei, HiSilicon

R1-2210924         On multi-cell PUSCH/PDSCH scheduling with a single DCI    Nokia, Nokia Shanghai Bell

R1-2211022         Discussion on multi-cell scheduling vivo

R1-2211045         Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI               ZTE

R1-2211063         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI Google Inc.

R1-2211082         Consideration on multi-cell PUSCH/PDSCH scheduling with a single DCI               Fujitsu

R1-2211213         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI CATT

R1-2211244         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI Spreadtrum Communications

R1-2211376         Discussion on the remaining issues for the multi-cell scheduling with a single DCI               xiaomi

R1-2211414         Discussions on multi-cell scheduling with a single DCI             Intel Corporation

R1-2211488         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI OPPO

R1-2211534         Discussion on multi-cell scheduling with a single DCI              China Telecom

R1-2211585         On multi-cell scheduling via a single DCI     Lenovo

R1-2211695         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI CMCC

R1-2211824         On multi-cell PUSCH/PDSCH scheduling with a single DCI    Apple

R1-2211878         Discussion on Multicarrier scheduling with a single DCI          FGI

R1-2211919         Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI               CAICT

R1-2211998         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI NTT DOCOMO, INC.

R1-2212060         On multi-cell PUSCH/PDSCH scheduling with a single DCI    Samsung

R1-2212132         Multi-cell PUSCH/PDSCH scheduling with a single DCI         Qualcomm Incorporated

R1-2212156         Multi-cell PUSCH/PDSCH scheduling with a single DCI         Ericsson

R1-2212190         Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI               Langbo

R1-2212252         On multi-cell PUSCH/PDSCH scheduling with a single DCI    MediaTek Inc.

R1-2212303         Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI               LG Electronics

R1-2212336         Discussion on multi-cell scheduling with a single DCI              ITRI

R1-2212362         Discussion on Multi-cell PXSCH scheduling with a single DCI              NEC

R1-2212392        Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI       Moderator (Lenovo)

From Nov 15th session

Agreement:

Confirm the RAN1#110bis-e working assumption with the following changes:

Working Assumption

For a set of cells which is configured for multi-cell scheduling,

·        Existing DCI size budget is maintained on each cell of the set of cells.

·        DCI size of DCI format 0_X/1_X is counted on one cell among the set of cells.

o   FFS which cell DCI size of the DCI format 0_X/1_X is counted on the reference cell.

·        BD/CCE of DCI format 0_X/1_X is counted on one cell among the set of cells.

o   FFS which cell BD/CCE of the DCI format 0_X/1_X is counted on the reference cell.

·        Same reference cell is used for both DCI format 0_X and DCI format 1_X.

·        The reference cell is

o   the scheduling cell if the scheduling cell is included in the set of cells and search space of the DCI format 0_X/1_X is configured only on the scheduling cell;

o   one cell of the set of cells which Ssearch space of DCI format 0_X/1_X is configured on one cell of the set of cells and associated with the search space of the scheduling cell with the same search space ID if search space of the DCI format 0_X/1_X is configured on the cell in addition to the scheduling cell.

§  FFS It is up to gNB on which cell the SS of the DCI format 0_X/1_X is configured on.

·        FFS: How tTo address Rel-17 BD/CCE limit for any given cell (operating the feature under Rel-17 BD/CCE limit)

o   For the reference cell, a total number of configured BD/CCEs for both DCI formats 0_X/1_X and legacy DCI formats (if configured) does not exceed the Rel-17 limits.

o   For other cells in the sets of cells, Rel-17 limits for PDCCH/DCI monitoring and BD/CCE counting rules for legacy DCI formats (not including DCI formats 0_X/1_X) apply

·        Note: This does not mean a UE is required to support number of BDs/CCEs beyond the Rel-17 limits (i.e.,  and ) for PDCCH candidates for each scheduled cell.

R1-2212393        Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI       Moderator (Lenovo)

From Nov 16th session

Agreement:

·         For a set of cells which is configured for multi-cell scheduling, up to 4 cells within the set of cells are supported.

o    A DCI format 0_X/1_X can schedule PUSCH(s)/PDSCH(s) on a combination of co-scheduled cells among the same set of cells.

R1-2212394        Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI       Moderator (Lenovo)

From Nov 18th session

Agreement

For DCI format 1_X/0_X,

·        Type-1 fields at least include below:

o   ChannelAccess-Cpext

o   TDRA

·        Below fields are agreed to be supported for DCI format 0_X/1_X. FFS: Whether the fields are type1, type2, type configurable, or omitted. FFS: details on the fields (e.g. length, which legacy configurations are applicable), other fields.

o   HARQ process number

o   MCS (FFS: potential compression scheme)

o   Bandwidth part indicator

o   Frequency domain resource assignment (FFS: potential compression scheme)

o   VRB-to-PRB mapping

o   PRB bundling size indicator

o   Rate matching indicator

o   ZP CSI-RS trigger

o   Antenna port(s)

o   Transmission configuration indication

o   DMRS sequence initialization

o   Frequency hopping flag

o   TPC command for scheduled PUSCH

o   Precoding information and number of layers

o   PTRS-DMRS association

o   SRS request

o   SRS resource indicator

o   SRS offset indicator

o   PTRS-DMRS association

o   Open-loop power control parameter set indication

o   UL/SUL indicator

Note: RAN1 strives to minimize the number of fields which are type configurable.

Agreement

For monitoring PDCCH candidates for a set of cells which is configured for multi-cell scheduling, the n_CI in the search space equation is determined by a value configured for the set of cells by RRC signaling.

R1-2212924        Feature lead summary#5 on multi-cell PUSCH/PDSCH scheduling with a single DCI       Moderator (Lenovo)

Agreement

The types for below fields in DCI format 1_X are listed (R1-2212924):

This does not imply that payload of DCI can be larger than what is supported for polar code in Rel-17.

FFS: Details

Agreement

The types for below fields in DCI format 0_X are listed:

This does not imply that payload of DCI can be larger than what is supported for polar code in Rel-17.

FFS: Details

9.9.22        Multi-carrier UL Tx switching scheme

R1-2210857         Discussion on multi-carrier UL Tx switching              Huawei, HiSilicon

R1-2211023         Discussion on UL TX switching     vivo

R1-2211046         Discussion on Multi-carrier UL Tx switching scheme ZTE

R1-2211064         Discussion on multi-carrier UL Tx switching scheme Google Inc.

R1-2211214         Discussion on multi-carrier UL Tx switching scheme CATT

R1-2211245         Discussion on multi-carrier UL Tx switching scheme Spreadtrum Communications

R1-2211285         On Multi-Carrier UL Tx Switching Nokia, Nokia Shanghai Bell

R1-2211377         Discussion on multi-carrier UL Tx switching scheme xiaomi

R1-2211489         Discussion on multi-carrier UL Tx switching scheme OPPO

R1-2211535         Discussion on UL Tx switching across up to 3 or 4 bands         China Telecom

R1-2211623         Considerations on Multi-carrier UL Tx switching scheme        Sony

R1-2211696         Discussion on multi-carrier UL Tx switching scheme CMCC

R1-2211825         On multi-carrier UL Tx switching   Apple

R1-2211999         Discussion on Multi-carrier UL Tx switching scheme NTT DOCOMO, INC.

R1-2212061         On multi-carrier UL Tx switching   Samsung

R1-2212133         Discussion on Rel-18 UL Tx switching         Qualcomm Incorporated

R1-2212157         Multi-carrier UL Tx switching        Ericsson

R1-2212251         On multi-carrier UL Tx switching scheme    MediaTek Inc.

R1-2212304         Discussion on Multi-carrier UL Tx switching scheme LG Electronics

R1-2212528        Summary#1 of discussion on multi-carrier UL Tx switching scheme               Moderator (NTT DOCOMO, INC.)

From Nov 15th session

Agreement:

For switched UL, if UE supports up to 2 ports UL transmission on all the bands in the band combination, only switching cases (Tx chain states) with 2T are assumed

·        Conclusion: In case of 3 bands, 3 switching cases ({2T,0T,0T}, {0T,2T,0T}, {0T,0T,2T}) are assumed

·        Conclusion: In case of 4 bands, 4 switching cases ({2T,0T,0T,0T}, {0T,2T,0T,0T}, {0T,0T,2T,0T}, {0T,0T,0T,2T}) are assumed

·        Based on the assumption, the switching gap is required for every UL transmission with changing transmitting band from preceding transmission in this scenario

Agreement:

For switched UL, if UE supports up to 2 ports UL transmission only on some of the bands in the band combination, only switching cases (Tx chain states) with 2T are assumed

·        Based on the assumption, the switching gap is required for every UL transmission with changing transmitting band from preceding transmission in this scenario

Agreement:

For dual UL, if a UE does not support concurrent transmission on specific band pair(s) and supports up to 2 ports UL transmission on all the bands in the band combination, corresponding switching case(s) with 1T-1T for the band pair(s) where concurrent transmission is not supported are not assumed.

Agreement:

For dual UL, if UE supports concurrent transmission on all band pairs and supports up to 2 ports UL transmission on all the bands in the band combination, all possible switching cases with 1T-1T and 2T are assumed

·        In case of 3 bands, 6 switching cases ({2T,0T,0T}, {0T,2T,0T}, {0T,0T,2T}, {1T, 1T, 0T}, {1T, 0T, 1T}, {0T, 1T, 1T}) are assumed.

·        In case of 4 bands, 10 switching cases ({2T,0T,0T,0T}, {0T,2T,0T,0T}, {0T,0T,2T,0T}, {0T,0T,0T,2T}, {1T,1T,0T,0T}, {1T,0T,1T,0T}, {1T,0T,0T,1T}, {0T,1T,1T,0T}, {0T,1T,0T,1T}, {0T,0T,1T,1T}) are assumed.

Agreement:

For dual UL, if UE supports up to 2 ports UL transmission only on some of the bands in the band combination, corresponding switching case(s) with 2T for the band where up to 2 ports transmission is not supported are assumed

·        If the UE does not support concurrent transmission on specific band pair(s) in the band combination, corresponding switching case(s) with 1T-1T for the band pair(s) where concurrent transmission is not supported are not assumed

Agreement:

Following new conditions are applicable to dual UL only (i.e., not applicable to switched UL)

·        When the UE is to transmit a 1-port or 2-port transmission on one uplink carrier on one band (1st band) and if Tx chain state at the preceding uplink transmission is 1T + 1T each on a carrier on other different bands (2nd and 3rd band)

·        When the UE is to transmit a 1-port + 1-port transmission each on one uplink carrier on different bands (1st and 2nd band) and if Tx chain state at the preceding uplink transmission is 2T on a carrier on another band (3rd band)

·        When the UE is to transmit a 1-port + 1-port transmission each on one uplink carrier on different bands (1st and 2nd band) and if Tx chain state at the preceding uplink transmission is 1T + 1T each on a carrier on one of the bands and another different band (1st or 2nd band, and 3rd band)

·        When the UE is to transmit a 1-port + 1-port transmission each on one uplink carrier on different bands (1st and 2nd band) and if Tx chain state at the preceding uplink transmission is 1T + 1T each on a carrier on other different bands (3rd and 4th band)

R1-2212757        Summary#2 of discussion on multi-carrier UL Tx switching scheme               Moderator (NTT DOCOMO, INC.)

From Nov 16th session

Agreement:

Following working assumption is confirmed with updates.

Working Assumption

At least for dual UL, reuse existing RRC parameter {oneT, twoT} via uplinkTxSwitching-DualUL-TxState to solve the issue on ambiguous switching state at least for following cases

·        Case#1 of the issue: two Tx chains are currently associated with band A, and next transmission is 1 port transmission on band B, but there are multiple possible switching cases where 1P on band B is supported

o   if twoT is indicated, both of two Tx chains are switched to band B

o   if oneT is indicated, one Tx chain is switched to band B while another Tx chain remains on band A

·          Case#2 of the issue: two Tx chains are currently associated with band A and B, and next transmission is 1 port transmission on band C, but there are multiple possible switching cases where 1P on band C is supported

o   if twoT is indicated, both of two Tx chains are switched to band C

o   if oneT is indicated, one Tx chain is switched to band C while how to determine the associated band for another Tx chain is FFS

§  Alt.1: based on gNB’s configuration/indication e.g., new RRC parameter

§  Alt.2: based on predefined rule

§  Other alternative is not precluded

·          FFS for other potential cases

Agreement:

In Case#2 where two Tx chains are currently associated with band A and B, and next transmission is 1 port transmission on band C, if oneT is indicated via uplinkTxSwitching-DualUL-TxState, one Tx chain is switched to band C and associated band for another Tx chain is determined by new RRC parameter which is down-selected from following alternatives.

·        An associated band is configured for each band so that another Tx chain is associated with the configured band (as associated band for the transmitting band)

o   E.g., associated band for each transmitting band is configured as {B for A}, {A for B}, {A for C} and {C for D}.

§  When 1 port transmission on band C is scheduled and Tx chains are currently associated with band A and B, Tx chain associated with band B is switched to band C while another Tx chain associated with band A remains unchanged (because band A is associated band for band C)

§  When 1 port transmission on band D is scheduled and Tx chains are currently associated with band A and B, Tx chain associated with band A (or B) is switched to band D while another Tx chain associated with band B (or A) is switched to band C (because band C is associated band for band D)

If there is one band where concurrent transmission with any other band is not supported, NW does not configure an associated band for the band. In such case, even if oneT is configured, UE performs switching as twoT is configured when 1 port transmission on the band is scheduled

Agreement:

There is no restriction on number of bands supporting up to 2 ports UL transmission for both switched UL and dual UL and for both 3 bands and 4 bands.

·        It is up to UE capability to support 2 ports UL transmission on none/some/all of the 3 or 4 bands

·        Note: UE with only 1 Tx chain is not expected to perform UL Tx switching (no spec impact)

R1-2212879        Summary#3 of discussion on multi-carrier UL Tx switching scheme               Moderator (NTT DOCOMO, INC.)

From Nov 18th session

Agreement

Confirm the following working assumption.

Working Assumption

Specify UL Tx switching schemes across up to 4 bands in Rel-18

Agreement

Following restrictions are applied for Rel-18 UL Tx switching across 3 or 4 bands.

• The UE does not expect to perform more than one uplink switching within a reference slot based on µ_UL = max(µ_{UL, 1}, µ_{UL, 2}, µ_{UL, 3}) in case of 3 bands, µ_UL = max(µ_{UL, 1}, µ_{UL, 2}, µ_{UL, 3}, µ_{UL, 4}) in case of 4 bands, where µ_{UL, 1}, µ_{UL, 2}, µ_{UL, 3}, µ_{UL, 4} are SCSs of active UL bandwidth parts of the bands in the band combination

o   If there are two consecutive intra-band carriers in one band, µ_{UL, 1} = max(µ_{UL, 1-1}, µ_{UL, 1-2}), where µ_{UL, 1-1} and µ_{UL, 1-2} are SCSs of active UL bandwidth parts of the carriers in the band

• (working assumption) If two uplink switching are triggered and result in UL transmissions on more than 2 bands within any two consecutive reference slots, then the time duration between the end of all transmission(s) prior to the first uplink switching and the start of all transmission(s) after the second uplink switching within the two reference slots is expected to be not less than a minimum separation time

o   The minimum separation time is a sum of X us and the switching gap required for the second uplink switching.

o   X us is subject to UE capability with a value set of {0us, 500us}

Final summary in R1-2212894.

 RAN1#112

9.9       Multi-carrier enhancements for NR

Please refer to RP-222251 for detailed scope of the WI.

[112-R18-MC_Enh] – Hiroki (NTT DOCOMO)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

9.9.1        Multi-cell PUSCH/PDSCH scheduling with a single DCI

R1-2300130         Discussion on multi-cell scheduling with a single DCI              Huawei, HiSilicon

R1-2300233         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI Spreadtrum Communications

R1-2300289         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI OPPO

R1-2300342         Discussion on Multi-cell PUSCH/PDSCH scheduling with a single DCI               ZTE

R1-2300365         On multi-cell PUSCH/PDSCH scheduling with a single DCI    Nokia, Nokia Shanghai Bell

R1-2300469         Discussion on multi-cell scheduling vivo

R1-2300591         Discussion on the remaining issues for the multi-cell scheduling with a single DCI               xiaomi

R1-2300696         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI CATT

R1-2300725         Remaining issues on multi-cell scheduling with a single DCI   China Telecom

R1-2300731         On multi-cell scheduling via a single DCI     Lenovo

R1-2300756         CSI request in case of multi-cell PUSCH scheduling  Fujitsu

R1-2300830         Discussion on Multi-cell PXSCH scheduling with a single DCI              NEC

R1-2300964         Discussions on multi-cell scheduling with a single DCI             Intel Corporation

R1-2301018         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI CMCC

R1-2301062         Discussions on multi-cell PUSCH/PDSCH scheduling with a single DCI               CAICT

R1-2301109         Discussion on Multi-cell PUSCH/PDSCH scheduling LG Electronics

R1-2301280         On multi-cell PUSCH/PDSCH scheduling with a single DCI    Samsung

R1-2301315         Remaining Issues on multi-cell PUSCH/PDSCH scheduling with a single DCI               Langbo

R1-2301321         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI ITRI

R1-2301362         On remaining issues for multi-cell PUSCH/PDSCH scheduling with a single DCI               Apple

R1-2301429         Multi-cell PUSCH/PDSCH scheduling with a single DCI         Qualcomm Incorporated

R1-2301509         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI NTT DOCOMO, INC.

R1-2301556         Multi-cell PUSCH/PDSCH scheduling with a single DCI         Ericsson

R1-2301563         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI Google Inc.

R1-2301601         On multi-cell PUSCH/PDSCH scheduling with a single DCI    MediaTek Inc.

R1-2301091        Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI       Moderator (Lenovo)

From Tuesday session

Agreement

For Type-2 HARQ-ACK codebook, for a set of cells which is co-scheduled by a DCI format 1_X, the reference PDSCH to determine DAI counting is the PDSCH with smallest serving cell index among the set of co-scheduled cells.

Agreement

·        For a set of cells which is co-scheduled by a DCI format 1_X, the PDSCH with the smallest serving cell index among the set of co-scheduled cells is used to determine last DCI format for PUCCH determination among DCI formats within a same PDCCH MO.

·        It is up to gNB implementation to resolve the last DCI format issue when both DCI format 1_X and other DCI format 1_0/1_1/1_2/1_X are received in a same PDCCH monitoring occasion on a same scheduling cell for scheduling PDSCHs on same scheduled cell.

Agreement

For determining the timing of a PUCCH carrying HARQ-ACK information corresponding to a set of co-scheduled PDSCHs by a DCI format 1_X, the reference PDSCH is the PDSCH ending last as indicated in the DCI format 1_X among the set of co-scheduled PDSCHs.

Conclusion

Type-1 HARQ-ACK codebook is supported for multi-cell scheduling without K1 extension.

·        UE expects HARQ-ACK information for all co-scheduled PDSCHs by DCI format 1_X can be mapped in the Type-1 HARQ-ACK codebook.

·        Type-1 HARQ-ACK codebook is not enhanced for Rel-18 multi-cell scheduling.

Agreement

For a set of cells which is configured for multi-cell scheduling using DCI format 0_X/1_X, a joint TDRA table is configured by RRC signaling for the set of cells with each row in the table containing TDRA indexes for all cells within the set of cells.

·        TDRA field in the DCI format 0_X/1_X belongs to Type-1B field.

·        TDRA field in the DCI format 0_X/1_X indicates a row from the joint TDRA table.

·        TDRA index for a cell points to a corresponding TDRA in the TDRA table applicable for DCI format 0-1/1-1.

Agreement

CSI request in DCI format 0_X belongs to Type-1C field.

·        This field is applied to the cell with smallest serving cell index among the co-scheduled cells.

Agreement

UL-SCH indicator in DCI format 0_X belongs to Type-1C field.

·        This field is applied to the cell with smallest serving cell index among the co-scheduled cells.

Agreement

Enhanced Type-3 codebook indicator in DCI format 1_X belongs to Type-1A field.

Agreement

HARQ-ACK retransmission indicator in DCI format 1_X belongs to Type-1A field.

Agreement

PUCCH Cell indicator in DCI format 1_X belongs to Type-1A field.

R1-2301092        Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI       Moderator (Lenovo)

From Wednesday session

Agreement

• For a set of cells configured for multi-cell scheduling using DCI format 0_X/1_X,
• the size of a Type-1A field in the DCI format 0_X/1_X is determined as maximum field size of active BWP among all cells within the set of cells.
• the size of a Type-1B field in the DCI format 0_X/1_X is equal to ceiling(log₂(N)), where N is the number of rows in RRC-configured table with each row containing multiple indexes for all cells within the set of cells.
• The Type-1B field indicates one row of the configured table
• The Type-1B index for a cell points to a corresponding index in a RRC configured table applicable for DCI format 0_1/1_1 or MAC CE activated values.
• the size of a per cell Type-2 field in the DCI format 0_X/1_X is determined based on active BWP for each cell.

Agreement

For a set of cells which is configured for multi-cell scheduling using DCI format 0_X and DCI format 1_X, support the following: 

• If table defining combinations of co-scheduled cells for the set of cells is configured,
• an indicator in the DCI is included and points to one row of the table.
• The table is configured by RRC signaling for the set of cells.
• Separate tables are configured for downlink scheduling and uplink scheduling
• The size of the indicator is equal to ceil(log2(N)), where N is the number of rows in the table.
• The max number of rows in the table is 16
• The size of the per-cell Type 2 fields for each co-scheduled cell does not change according to the indicated co-scheduled cell combination
• The payload size of DCI format 1_X is derived by UE based on RRC configuration of the active BWP(s) of co-scheduled cell combinations within the set of cells.

§  The payload size of DCI format 1_X is the same for the active BWP(s) of all the co-scheduled cell combinations and equal to the largest payload size among the active BWP(s) of all the co-scheduled cell combinations determined by the co-scheduled cell combination table.

• The payload size of DCI format 0_X is derived by UE based on RRC configuration of the active BWP(s) of co-scheduled cell combinations within the set of cells.

§  The payload size of DCI format 0_X is the same for the active BWP(s) of all the co-scheduled cell combinations and equal to the largest payload size among the active BWP(s) of all the co-scheduled cell combinations determined by the co-scheduled cell combination table.

• Otherwise,
• The UE determines the actually scheduled cell(s) based on the FDRA field of each cell of the set of cells.
• For Type 0 FDRA, all 0s indicates the cell is not scheduled.
• For Type 1 FDRA, all 1s indicates the cell is not scheduled.
• The size of the Type 2 fields for each cell does not change according to actually co-scheduled cells.
• The payload size of DCI format 0_X is derived by UE based on RRC configuration of the active BWP(s) of all cells within the set of cells.
• The payload size of DCI format 1_X is derived by UE based on RRC configuration of the active BWP(s) of all cells within the set of cells.

Agreement

Following is supported in Rel-18 multi-cell scheduling

• A UE can be configured one or multiple sets of cells with each set configured for multi-cell scheduling using DCI format 0_X/1_X.
• Up to 4 sets of cells can be configured per PUCCH group.
• When multiple sets of cells are configured,
• a cell in one set of cells can’t be included in another set of cells.
• n_CI value is independently configured for each set of cells.
• reference cell for counting DCI size and BD/CCE of DCI format 0_X/1_X is independently determined for each set of cells.
• search space configuration of DCI format 0_X/1_X is independently configured for each set of cells.
• DCI size of DCI format 0_X is independently determined for each set of cells.
• DCI size of DCI format 1_X is independently determined for each set of cells.
• The multiple sets of cells can be scheduled by DCI format 0_X/1_X from different scheduling cells.
• Up to N sets of cells can be configured and respectively scheduled by DCI format 0_X/1_X from a same scheduling cell.
• The value of N is reported as UE capability.
• An indicator is included in the DCI to indicate the scheduled set of cells,
• The size of the indicator is equal to ceil(log2(N)), where N is the number of sets of cells.
• Unique n_CI value is configured for each set of cells.

R1-2301093        Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI       Moderator (Lenovo)

From Thursday session

Agreement

·        A new RBG size configuration “Configuration 3” is added with the following values and only used for DCI format 0_X/1_X for RA type 0.

·        RBG size is configured per BWP per cell.

·        Independent RA type configuration is applied per BWP per cell for multi-cell scheduling DCI.

Table 5.1.2.2.1-1 / Table 6.1.2.2.1-1: Nominal RBG size P

Agreement

DCI format 0_X / 1_X with CRC scrambled by C-RNTI and MCS-C-RNTI is supported.

Agreement

For a set of cells which is configured for multi-cell scheduling using DCI format 0_X/1_X, if DCI size budget on the reference cell can’t be maintained after performing Rel-17 DCI size alignment procedures for legacy DCI formats (after step 4C), UE applies zero padding to whichever of DCI formats 0_X or 1_X that has a smaller size to have equal size.

Agreement

• Separate search space sets for DCI format 0_X/1_X and legacy DCI formats are independently configured
• Separate search space sets for DCI format 0_X and 1_X can be independently configured

Agreement

If the UE is configured with two SRS resource sets with ‘codebook’ or ‘non-codebook’, a PUSCH scheduled by DCI format 0_X is always associated with the first SRS resource set with ‘codebook’ or ‘non-codebook’.

Conclusion

PUSCH repetition Type B operation is not supported with DCI format 0_X (i.e. UE cannot be configured with PUSCH repetition Type B applicable for DCI format 0_1)

R1-2301094        Feature lead summary#4 on multi-cell PUSCH/PDSCH scheduling with a single DCI       Moderator (Lenovo)

From Friday session

Agreement

New RRC parameter of RBG granularity for RA type 1 can be configured per BWP per cell for DCI format 0_X/1_X with same value range applicable for DCI 0_2/1_2.

Agreement

Size of RV field can be configured per BWP per cell for DCI format 0_X/1_X.

Agreement

Size of HPN field can be configured per BWP per cell for DCI format 0_X/1_X.

Agreement

• Priority indicator in DCI format 0_X belongs to Type-1A field.
• The indicated priority is applied to all the co-scheduled PUSCH(s)
• Priority indicator in DCI format 1_X belongs to Type-1A field.
• The indicated priority indicator is applied to the PUCCH.
• RRC parameters is introduced to configure the presence of priority indicator in DCI format 0_X/1_X
• This parameter is per set of cells

Agreement

• ChannelAccess-Cpext in DCI format 1_X belongs to Type-1A field.
• The indicated channel access information is applied to the PUCCH and/or SRS (whichever is first).
• ChannelAccess-Cpext-CAPC in DCI format 0_X belongs to Type-1A field.
• The indicated code point is applied to all the co-scheduled PUSCHs and/or SRS (whichever is first) by DCI format 0_X.

Agreement

Beta_offset indicator in DCI format 0_X belongs to Type-1A field.

• This field is applied to the scheduled PUSCH(s) where the UCI is multiplexed.

Agreement

Inclusion of SCell dormancy indication in DCI format 0_X/1_X is configurable.

Agreement

Inclusion of PDCCH monitoring adaptation indication in DCI format 0_X/1_X is configurable.

Agreement

Inclusion of minimum applicable scheduling offset indicator in DCI format 0_X/1_X is configurable.

Friday before closing:

Proposal 3-14 on UL/SUL indicator was debated. Extensively discussed in RAN1 and no consensus could be achieved. Some companies commented that the proposal was not in line with the WI objectives laid down in RP-223553. The issue is to be brought to plenary for further progress/decision.

9.9.22        Multi-carrier UL Tx switching scheme

R1-2300131         Discussion on multi-carrier UL Tx switching              Huawei, HiSilicon

R1-2300234         Discussion on multi-carrier UL Tx switching scheme Spreadtrum Communications

R1-2300290         Discussion on multi-carrier UL Tx switching scheme OPPO

R1-2300343         Discussion on Multi-carrier UL Tx switching scheme ZTE

R1-2300470         Discussion on UL TX switching     vivo

R1-2300492         Discussion on remaining issues of multi-carrier UL Tx switching           FGI

R1-2300592         Discussion on multi-carrier UL Tx switching scheme xiaomi

R1-2300697         Discussion on multi-carrier UL Tx switching scheme CATT

R1-2300726         Remaining issues on UL Tx switching across up to 3 or 4 bands             China Telecom

R1-2301019         Discussion on multi-carrier UL Tx switching scheme CMCC

R1-2301059         On Multi-Carrier UL Tx Switching Nokia, Nokia Shanghai Bell

R1-2301110         Discussion on Multi-carrier UL Tx switching scheme LG Electronics

R1-2301281         On multi-carrier UL Tx switching   Samsung

R1-2301363         On remaining issues for multi-carrier UL Tx switching             Apple

R1-2301430         Discussion on Rel-18 UL Tx switching         Qualcomm Incorporated

R1-2301842         Discussion on Multi-carrier UL Tx switching scheme NTT DOCOMO, INC.       (rev of R1-2301510)

R1-2301557         Multi-carrier UL Tx switching        Ericsson

R1-2301564         Discussion on multi-carrier UL Tx switching scheme Google Inc.

R1-2301801        Summary#1 of discussion on multi-carrier UL Tx switching scheme               Moderator (NTT DOCOMO, INC.)

Presented in Wednesday session

R1-2302114        Summary#2 of discussion on multi-carrier UL Tx switching scheme               Moderator (NTT DOCOMO, INC.)

From Friday session

Agreement

Confirm the working assumption with following updates

(working assumption) If two uplink switching are triggered and UL transmissions involved in the two uplink switching are on more than 2 bands within any two consecutive reference slots, then the time duration between the end start of all transmission(s) prior toafter the first uplink switching and the start of all transmission(s) after the second uplink switching within the two reference slots is expected to be not less than a minimum separation time

·        The minimum separation time is a summaximum of X us and the switching gap required for the second uplink switching.

·        X us is subject to UE capability with a value set of {0us, 500us}

Agreement

Alt.5: gNB configures priorities to each carrier/band.

·        The gNB configures priority for each band. The UE determines the switching period location on either switching-from band(s) or switching-to band(s) that is involved in the UL Tx switching and is not with the highest priority band.

Final summary in R1-2302221.

 RAN1#114-bis

8.12   Maintenance on Multi-Carrier Enhancements for NR

[114bis-R18-MC_Enh] – Hiroki (NTT DOCOMO)

Email discussion on multi-carrier enhancement for NR

-        To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

8.12.1    Multi-cell PUSCH/PDSCH scheduling with a single DCI

R1-2308919         Maintenance of multi-cell PDSCCH/PUSCH scheduling with a single DCI            Huawei, HiSilicon

R1-2308998         Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI         Spreadtrum Communications

R1-2309089         Remaining issues on Rel-18 Multi-cell scheduling      vivo

R1-2309136         Maintenance of Multi-cell PUSCH/PDSCH scheduling with a single DCI            ZTE

R1-2309171         On Rel-18 MC-DCI scheduling       Nokia, Nokia Shanghai Bell

R1-2309306         Remaining issues on Multi-cell scheduling with single DCI      LG Electronics

R1-2309391         Remaining Issues on multi-cell PUSCH/PDSCH scheduling with a single DCI         Samsung

R1-2309432         Discussion on multi-cell PUSCH/PDSCH scheduling with a single DCI            xiaomi

R1-2309502         Maintenance on Multi-cell PUSCH/PDSCH scheduling with a single DCI            CATT

R1-2309623         Remaining issues for multi-cell PUSCH/PDSCH scheduling with a single DCI         OPPO

R1-2309642         Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI         Fujitsu

R1-2309685         Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI         CMCC

R1-2309698         Remaining issues on Rel-18 multi-cell scheduling      Lenovo

R1-2309709         Remaining issues on multi-cell PUSCH/PDSCH scheduling              ETRI

R1-2309847         On remaining issues for Rel-18 multi-cell scheduling Apple

R1-2309875         Remaining detail on multi-cell scheduling with a single DCI              ITRI

R1-2309972         On maintenance for multi-cell scheduling with a single DCI              MediaTek Inc.

R1-2310010         Remaining Issues on multi-cell PUSCH/PDSCH scheduling with a single DCI         Langbo

R1-2310047         Maintenance on multi-cell PUSCH/PDSCH scheduling with a single DCI            NTT DOCOMO, INC.

R1-2310097         Maintenance for single DCI scheduling multiple cells Ericsson

R1-2310156         Multi-cell PUSCH/PDSCH scheduling with a single DCI              Qualcomm Incorporated

R1-2310393         Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI         Moderator (Lenovo)

From Tuesday session

Agreement

For a serving cell included in MC-DCI-SetofCells, a UE does not expect to be configured to monitor PDCCH candidates on more than one scheduling cell for detection of DCI formats scheduling the serving cell.

Agreement

DCI format level padding is adopted for DCI format 0_3 or DCI format 1_3.

Agreement

For DCI format 0_3, when ScheduledCellCombo-ListDCI-0-3 is not configured, all '0's for FDRA Type 2 with μ=1 or all ‘1’s for FDRA Type 2 with μ=0 indicates the corresponding cell is not scheduled.

Agreement

Below TP on TS38.213-i00 is adopted.

·       Reason for change: PDCCH monitoring adaptation indication is applicable for PDCCH monitoring on a serving cell and captured in DCI format 0_3/1_3 in 38.212-i00. However, TS38.213-i00 does not reflect it.

·       Summary of change: Add DCI format 0_3 and DCI format 1_3 in Section 10 on PDCCH skipping and SSSG switching.

·       Consequence if not approved: Inconsistency between TS38.212 and TS38.213.

Agreement

The Minimum applicable scheduling offset indicator, if configured to be present in DCI format 0_3/1_3, is of Type-1A field with 1 bit.

Below TP on TS38.212-i00 is adopted.

·       Reason for change: RAN1 has agreed that inclusion of minimum applicable scheduling offset indicator is supported in DCI format 0_3/1_3 and this field is already captured in 38.212-i00. However, the bit size is not defined.

·       Summary of change: Add the clarification to this field when the bit size is equal to 1.

·       Consequence if not approved: Bit size of this field is not defined in TS38.212.

Agreement

Simultaneous configuration of both multicast reception and multi-cell scheduling in the same PUCCH group is not supported in Rel-18.

Agreement

For an enhanced Type-3 HARQ-ACK codebook triggered by a DCI format 1_3, if the enhanced Type-3 HARQ-ACK codebook indicator is not configured, the MCS field of TB1 corresponding to a cell with smallest serving cell index among the co-scheduled cells with invalid FDRA field values is used to indicate the index of the enhanced Type-3 HARQ-ACK codebook.

·       Note: Cells with valid FDRA fields are scheduled

Agreement

For HARQ-ACK retransmission triggered by a DCI format 1_3, the MCS field of TB1 corresponding to a cell with smallest serving cell index among the co-scheduled cells with invalid FDRA field values is used to indicate the value of slot level offset l.

·       Note: Cells with valid FDRA fields are scheduled

R1-2310394         Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI         Moderator (Lenovo)

From Wednesday session

Agreement

The value range of SRS-RequestCombo is BIT STRING (2..3).

Agreement

·       Single joint table is configured per set of cells for each of Type-1B fields other than TDRA (i.e., rateMatchListDCI-1-3, zp-CSI-RSListDCI-1-3, tci-ListDCI-1-3, srs-RequestListDCI-1-3, srs-OffsetListDCI-1-3, srs-RequestListDCI-0-3, srs-OffsetListDCI-0-3).

o   Entries for each CC are interpreted based on the new/target BWPs per cell that is indicated by the BWP indicator field of DCI 0_3/1_3.

·       Single joint table is configured per set of cells for TDRA (i.e., TDRA-FieldIndexListDCI-1-3, TDRA-FieldIndexListDCI-0-3).

o   Entries of the joint table for TDRA (i.e., TDRA-FieldIndexDCI-1-3) are configured for each BWP of each CC.

o   Columns of the indicated entry corresponding to the new/target BWPs per cell that is indicated by the BWP indicator field of DCI 0_3/1_3 are applied.

·       The maximum size of TDRA-FieldIndexListDCI-1-3 is 32.

·       The maximum size of TDRA-FieldIndexListDCI-0-3 is 64.

Agreement

Below TP on TS38.212-i00 is adopted.

·       Reason for change: RAN1 has agreed that inclusion of SCell dormancy indication is supported in DCI format 0_3/1_3 and this field is already captured in 38.212-i00. However, the bit size is not defined.

·       Summary of change: Add the clarification on the bit size of this field in Section 7.3.1.14 in TS38.212.

·       Consequence if not approved: Bit size of this field is not defined in TS38.212.

Agreement

For MC-DCI, SCell dormancy indication Case 1 (for both DCI format 0-3 and 1-3) and Case 2 (only for DCI format 1-3) are supported.

R1-2310395         Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI         Moderator (Lenovo)

From Friday session

Agreement

For a UE configured with a set of cells by MC-DCI-SetofCells,

·       If the scheduling cell is active while the reference cell is indicated dormant or deactivated, the UE does not monitor DCI format 0_3/1_3 on the scheduling cell for the set of cells.

Final summary in R1-2310651.

8.12.22    Multi-carrier UL Tx switching scheme

R1-2308920         Maintenance of multi-carrier UL Tx switching schemes              Huawei, HiSilicon

R1-2308999         Remaining issues on UL Tx switching          Spreadtrum Communications

R1-2309090         Remaining issues on Rel-18 UL Tx switching across 3 or 4 bands              vivo

R1-2309137         Maintenance of Multi-carrier UL Tx switching scheme              ZTE

R1-2309307         Remaining issues on Multi-carrier UL Tx switching scheme    LG Electronics

R1-2309433         Remaining issues on multi-carrier UL Tx switching scheme              xiaomi

R1-2309503         Maintenance on Multi-carrier UL Tx switching scheme              CATT

R1-2309557         Remaining issues on Rel-18 UL Tx switching             China Telecom

R1-2309624         Remaining issues on multi-carrier UL Tx switching scheme              OPPO

R1-2309686         Remaining issues on multi-carrier UL Tx switching scheme              CMCC

R1-2309848         On remaining issues for Rel-18 UL Tx switching        Apple

R1-2309922         Remaining issues for R18 multi-carrier UL Tx switching              MediaTek Inc.

R1-2309923         On remaining issues of Multi-carrier UL Tx switching CR to 38.214   Nokia, Nokia Shanghai Bell

R1-2310048         Maintenance on multi-carrier UL Tx switching scheme              NTT DOCOMO, INC.

R1-2310157         Discussion on Rel-18 UL Tx switching         Qualcomm Incorporated

R1-2310257         On Maintenance for Multi-Carrier UL TX switching  Ericsson

R1-2310380         Summary of discussion on Multi-carrier UL Tx switching scheme  Moderator (NTT DOCOMO, INC.)

From Tuesday session

Agreement

For the specification (latest draft CR from the editor) of minimum separation time in TS38.214, remove the description “or the capability is not reported by the UE,”

Agreement

Send the RAN1 recommendation on the update of TS38.300 to RAN2/4 as below.

In uplink CA or SUL, a UE configured with uplink Tx switching can have Tx chain(s) dynamically switched from one uplink carrier band or two uplink bands to another uplink carrier band or two uplink bands for enabling up to 2Tx UL transmission on that carrierin one uplink band or simultaneous UL transmissions in two uplink bands at a time.

Comeback on LS.

R1-2310491         Draft LS on TS38.300 TP for UL Tx switching in Rel-18              Moderator (NTT DOCOMO, INC.)

Wednesday decision: The draft LS is endorsed. Final LS is approved in R1-2310492.

R1-2310490         Summary#2 of discussion on Multi-carrier UL Tx switching scheme  Moderator (NTT DOCOMO, INC.)

From Wednesday session

Conclusion

When UE is configured with 3 or 4 bands for Rel-18 UL Tx switching, it is RAN1 understanding that the determination of switching period location is based on the band priority even for the switching involving only 2 bands.

Agreement

For the TS38.214, conditions for triggering switch and descriptions on determination of the length of switching period for different switching cases with dual uplink with more than two bands involved in one uplink TX switching,

·       Alt.3: it is kept in both TS38.214 and TS38.101-1 (TS38.214 refers TS38.101-1 and vice versa)

o   From RAN1 point of view, conditions for triggering switching is in TS38.214, and the length determination of switching period should be in TS38.101-1.

o   Send an LS to RAN4 to reflect the above in their specification.

R1-2310582         Summary#3 of discussion on Multi-carrier UL Tx switching scheme  Moderator (NTT DOCOMO, INC.)

From Friday session

R1-2310583         Draft LS on conditions for triggering switch and descriptions on determination of the length of switching period in specifications Moderators (NTT DOCOMO, INC.)

Decision: The draft LS is endorsed. Final version is approved in R1-2310584.

Agreement

Update the RAN1 agreement made at RAN1#112 meeting as below and send LS to RAN4/2 to inform the updated agreement.

Alt.5: gNB configures priorities to each carrier/band.

• The gNB configures priority for each band. The UE determines the switching period location on either switching-from band(s) or switching-to band(s) that is involved in the UL Tx switching and is not with the highest priority band among set of bands, where each band in the set satisfies the following condition:
• (for switched UL) is contained in either switching-from band(s) or switching-to band(s) (not both) with actual transmission.
• (for dual UL) is contained in either switching-from band(s) or switching-to band(s) (not both) with or without actual transmission

R1-2310678         Draft LS on determination of switching period location in frequency domain based on band priority Moderators (NTT DOCOMO, INC.)

Decision: The draft LS to RAN4/RAN2 is endorsed. Final version is approved in R1-2310679.

Final summary in R1-2310677.

 RAN1#115

8.12   Maintenance on Multi-Carrier Enhancements for NR

[115-R18-MC_Enh] – Hiroki (NTT DOCOMO)

Email discussion on multi-carrier enhancement for NR

-        To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2312541         Summary of discussion on higher layer parameters list for MCE              Moderator (NTT DOCOMO, INC.)

8.12.1    Multi-cell PUSCH/PDSCH scheduling with a single DCI

R1-2310887         Maintenance of multi-cell PDSCCH/PUSCH scheduling with a single DCI            Huawei, HiSilicon

R1-2311024         Maintenance of Multi-cell PUSCH/PDSCH scheduling with a single DCI            ZTE

R1-2311046         Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI         Fujitsu

R1-2311110         Remaining issues on Rel-18 Multi-cell scheduling      vivo

R1-2311177         Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI         Spreadtrum Communications

R1-2311275         Remaining issues for multi-cell PUSCH/PDSCH scheduling with a single DCI         OPPO

R1-2311323         Maintenance on Multi-cell PUSCH/PDSCH scheduling with a single DCI            CATT

R1-2311387         Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI         xiaomi

R1-2311496         Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI         CMCC

R1-2311520         On Rel-18 MC-DCI scheduling       Nokia, Nokia Shanghai Bell

R1-2311552         Remaining issues on multi-cell scheduling with a single DCI              China Telecom

R1-2311587         Remaining issues on Rel-18 multi-carrier enhancements              Lenovo

R1-2311634         Maintenance on multi-cell PUSCH/PDSCH scheduling with a single DCI            NTT DOCOMO, INC.

R1-2311698         On remaining issues for Rel-18 multi-cell scheduling Apple

R1-2311735         Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI         Langbo

R1-2311758         Remaining issues on multi-cell PUSCH/PDSCH scheduling              ETRI

R1-2311860         Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI         Samsung

R1-2311899         Remaining issues on Multi-cell scheduling with single DCI      LG Electronics

R1-2311990         On maintenance for multi-cell scheduling with a single DCI              MediaTek Inc.

R1-2312049         Multi-cell PUSCH/PDSCH scheduling with a single DCI              Qualcomm Incorporated

R1-2312102         Maintenance for single DCI scheduling multiple cells Ericsson

R1-2312115         Remaining detail on multi-cell scheduling PUSCH/PDSCH with a single DCI            ITRI

R1-2312360         Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI         Moderator (Lenovo)

From Tuesday session

Agreement

The combination of DCI format 0_3 and Rel-17/18 PUSCH coverage enhancements (DWS, TBoMS, Available Slot counting, DM-RS bundling) is not supported.

Friday decision: Tuesday above agreement is replaced by:

Conclusion

There is no consensus to support TPI field for DCI format 0_3 in Rel-18.

Agreement

For a UE configured with a set of cells by MC-DCI-SetofCells,

·       If an SCell within the set of cells is deactivated and its firstActiveDownlinkBWP-Id is not set to dormant BWP, the UE determines the sizes of fields in DCI format 1_3 according to the DL BWP provided by firstActiveDownlinkBWP-Id.

·       If an SCell within the set of cells is dormant, or if an SCell within the set of cells is deactivated and its firstActiveDownlinkBWP-Id is set to dormant BWP,

o   the UE determines the sizes of fields in DCI format 1_3 according to the DL BWP provided by firstWithinActiveTimeBWP-Id for the SCell if provided;

o   otherwise, according to the DL BWP provided by firstOutsideActiveTimeBWP-Id for the SCell.

·       If an SCell within the set of cells is deactivated, the UE determines the sizes of fields in DCI format 0_3 according to the UL BWP provided by firstActiveUplinkBWP-Id.

Agreement

·       Adopt the following TP to 38.214 for the support of FDRA Type 2 for PUSCH scheduled by DCI format 0_3:

Agreement

·       When Antenna port(s) field in DCI format 1_3 is configured as type1a, UE expects to be configured with a common table from Tables 7.3.1.2.2-1/2/3/4 in TS38.212 is used for all cells in set of cells.

o   The DMRS mapping type should be the same across the cells in set of cells.

·       When Antenna port(s) field in DCI format 0_3 is configured as type1a, UE expects to be configured with a common table from Tables 7.3.1.1.2-6, 7.3.1.1.2-6A, 7.3.1.1.2-7, 7.3.1.1.2-7A, 7.3.1.1.2-8, 7.3.1.1.2-9, 7.3.1.1.2-10, 7.3.1.1.2-11, 7.3.1.1.2-12, 7.3.1.1.2-13, 7.3.1.1.2-14, 7.3.1.1.2-15, 7.3.1.1.2-16, 7.3.1.1.2-17, 7.3.1.1.2-18, 7.3.1.1.2-19, 7.3.1.1.2-20, 7.3.1.1.2-21, 7.3.1.1.2-22, 7.3.1.1.2-23, 7.3.1.1.2-24, and 7.3.1.1.2-25 in TS38.212 is used for all cells in set of cells.

o   The DMRS mapping type should be the same across the cells in set of cells.

·       When TPMI field in DCI format 0_3 is configured as type1a, UE expects to be configured with a common table from Tables 7.3.1.1.2-2, 7.3.1.1.2-2A, 7.3.1.1.2-B, 7.3.1.1.2-3, 7.3.1.1.2-3A, 7.3.1.1.2-4, 7.3.1.1.2-4A, 7.3.1.1.2-5, and 7.3.1.1.2-5A in TS38.212 is used for all cells in set of cells.

·       When SRI field in DCI format 0_3 is configured as type1a, UE expects to be configured with a common table from Tables 7.3.1.1.2-28, 7.3.1.1.2-29, 7.3.1.1.2-30, 7.3.1.1.2-31, 7.3.1.1.2-32, 7.3.1.1.2-32A, and 7.3.1.1.2-32B in TS38.212 is used for all cells in set of cells.

Agreement

For a UE configured with DCI format 1_3, the number of HARQ-ACK bits used for PUCCH power control is derived based on a summation of the corresponding numbers of HARQ-ACK bits in the two HARQ-ACK sub-codebooks.

R1-2312361         Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI           Moderator (Lenovo)

R1-2312362         Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI         Moderator (Lenovo)

From Wednesday session

Agreement

For a DCI format 1_3 transmitted on PCell, if one-shot HARQ-ACK request is not present or set to '0', and if HARQ-ACK retransmission indicator is not present or set to ‘0’, SCell dormancy indication is provided by repurposing below fields corresponding to one or more serving cell with the smallest cell index with invalid FDRA values in ascending order of serving cell index:

·       Modulation and coding scheme of transport block 1

·       NDI of transport block 1

·       Redundancy version of transport block 1

·       HARQ process number

·       Antenna port(s) if AntennaPortsDCI1-3 is configured as ‘type2’

Note: Cells with valid FDRA fields are scheduled.

Agreement

Rel-18 specifications support a DCI format 1_3 is transmitted without scheduling any PDSCH for SCell dormancy indication.

·       For Type-2 HARQ-ACK codebook, the corresponding HARQ-ACK information for the DCI format 1_3 is included in the first Type-2 sub-codebook.

Agreement

For a cell provided in MC-DCI-SetofCells, when no search space set is configured for the cell, the cell is not counted as a scheduled cell for M_total_μ/C_total_μ calculation.

Agreement

·       BWP indicator in a DCI format 0_3/1_3 applies only to the scheduled cell(s) with valid FDRA value(s).

·       For a cell scheduled by DCI format 0_3/1_3 with valid FDRA value, if the BWP indicator indicates a code point that does not correspond to a configured BWP for the cell, the UE does not perform dynamic BWP switching based on the BWP indicator and transmits/receives data on the current active BWP of the cell.

R1-2312513         Feature lead summary#4 on multi-cell PUSCH/PDSCH scheduling with a single DCI         Moderator (Lenovo)

From Thursday session

Agreement

In case of BWP switching

·       For a Type-2 field in a DCI format 0_3/1_3, the existing procedure for DCI field parsing (via truncation or zero-padding) is applied per “block” of the Type-2 field in the DCI format 0_3/1_3.

R1-2312514         Feature lead summary#5 on multi-cell PUSCH/PDSCH scheduling with a single DCI         Moderator (Lenovo)

From Friday session

Agreement

For Type-2 HARQ-ACK codebook, if a DCI format 1_3 is transmitted with fields repurposed for SCell dormancy indication and schedules one or more PDSCHs,

·       the corresponding HARQ-ACK information for the one or more PDSCHs is included in the second Type-2 HARQ-ACK sub-codebook.

·       HARQ-ACK information for the SCell dormancy indication is mapped to HARQ-ACK bit position for the serving cell with the smallest cell index with invalid FDRA and included in the second Type-2 HARQ-ACK sub-codebook.

8.12.22    Multi-carrier UL Tx switching scheme

R1-2310888         Maintenance of multi-carrier UL Tx switching schemes              Huawei, HiSilicon

R1-2311025         Maintenance of Multi-carrier UL Tx switching scheme              ZTE

R1-2311111         Remaining issues on Rel-18 UL Tx switching across 3 or 4 bands              vivo

R1-2311178         Remaining issues on UL Tx switching          Spreadtrum Communications

R1-2311276         Remaining issues on multi-carrier UL Tx switching scheme              OPPO

R1-2311324         Maintenance on Multi-carrier UL Tx switching scheme              CATT

R1-2311388         Remaining issues on multi-carrier UL Tx switching scheme              xiaomi

R1-2311466         On remaining issues of Multi-carrier UL Tx switching CR to 38.214   Nokia, Nokia Shanghai Bell

R1-2311497         Remaining issues on multi-carrier UL Tx switching scheme              CMCC

R1-2311553         Remaining issues on Rel-18 UL Tx switching             China Telecom

R1-2311635         Maintenance on multi-carrier UL Tx switching scheme              NTT DOCOMO, INC.

R1-2311699         On remaining issues for Rel-18 UL Tx switching        Apple

R1-2311900         Remaining issues on Multi-carrier UL Tx switching scheme    LG Electronics

R1-2311907         On Maintenance for Multi-Carrier UL TX switching  Ericsson

R1-2312050         Discussion on Rel-18 UL Tx switching         Qualcomm Incorporated

R1-2312284         Summary of discussion on Multi-carrier UL Tx switching scheme  Moderator (NTT DOCOMO, INC.)

From Tuesday session

Agreement

Following TP is adapted for TS38.214

Agreement

Following TP is adapted for TS38.214

Conclusion

Even if all cells in a band are deactivated, the band is counted in the determination of 2, 3 or 4 bands of UL Tx switching (i.e., Rel-16/17 or Rel-18 UL Tx switching is determined based on RRC configuration irrespective of activation/deactivation).

·       No TP is necessary for above.

Agreement

The following TP is agreed for TS38.214 clause 6.1.6.2.2

------- Start of TP ------

If the UE is configured with uplinkTxSwitching-DualUL-TxState set to 'oneT', when the UE is under the operation state in which 1-port transmission can be supported on one carrier on the 1st band and the 2nd band followed by no transmission on any carrier on these two bands and 1-port transmission on the other carrier on the 3rd band the UE shall consider this as if 1-port transmission was transmitted on the 3rd band and the band associated with the 3rd band as configured by associatedBand, otherwise the UE shall consider this as if 2-port transmission took place on the transmitting carrier. Even if all cells in a band are deactivated, that does not invalidate the associated band configuration that is indicating the band as associated band for the other band(s) for the definition in clause 6.1.6.

------- End of TP ------

R1-2312426         Summary#2 of discussion on Multi-carrier UL Tx switching scheme  Moderator (NTT DOCOMO, INC.)

From Wednesday session

Conclusion

·       If all cells in a band are deactivated, the SCS of the deactivated SCell is not considered for the reference slot determination.

·       If all cells in a band are dormant, the SCS of the dormant SCell is not considered for the reference slot determination.

Agreement

The following TP is agreed for TS38.214 clause 6.1.6

------------- Start of TP -------------

The UE may omit uplink transmission during the uplink switching gap  if the conditions defined in this clause are met and the UE is configured with uplinkTxSwitching. The switching gap  is indicated by UE capability uplinkTxSwitchingPeriod2T2T if uplinkTxSwitching-2T-Mode is configured, and uplinkTxSwitchingPeriod otherwise in clauses 6.1.6.1, 6.1.6.2.0, 6.1.6.3, and is determined withbased on UE capability uplinkTxSwitchingPeriodForBandPair in clause 6.1.6.2.2 for uplink switching with 3 or 4 uplink bands:

·        If a UE indicated a capability for uplink switching with BandCombination-UplinkTxSwitch for a band combination, and if it is for that band combination

o    Configured with a MCG using E-UTRA radio access and with a SCG using NR radio access (EN-DC), or

o    Configured with uplink carrier aggregation, or

o    Configured in a serving cell with two uplink carriers with higher layer parameter supplementaryUplink.

The conditions under which the switching gap may be present are defined for each of the cases in clauses 6.1.6.1, 6.1.6.2, and 6.1.6.3 respectively.

------------- End of TP -------------

Agreement

Following TP is agreed for TS38.214

R1-2312517         Summary#3 of discussion on Multi-carrier UL Tx switching scheme  Moderator (NTT DOCOMO, INC.)

From Thursday session

Conclusion

·       In case 2 ports transmission on band B is not supported but twoT is indicated and the switching is performed from 1T+1T on band A+C to 1 port transmission on band B, another Tx chain is also assumed to be switched to band B.

·       In case 2 ports transmission on band B is not supported but twoT is indicated and the switching is performed from 2T on band A to 1 port transmission on band B, another Tx chain is also assumed to be switched to band B.

Conclusion

In case SwitchedUL is configured for band pair A+B but oneT is indicated and the switching is performed from 2T on band A to 1 port transmission on band B, another Tx chain is also assumed to be switched to band B as specified in TS38.214 6.1.6.2.0.

R1-2312694         Summary#6 of discussion on Multi-carrier UL Tx switching scheme  Moderator (NTT DOCOMO, INC.)

From Friday session

Agreement

Following TP is agreed.

·       Note: this does not change previous RAN1 agreements

Agreement

For UL Tx switching, if an UL transmission with starting symbol at T0 is scheduled to a UE, the UE is not expected to be scheduled with another UL transmission overlapping with the first UL transmission in time and resulting in interruption on the first UL transmission by a DCI arriving later than T0-Toffset.

·       FFS: whether any specification impact is needed considering the existing cut-off time specified in S6.1.6 of TS 38.214.

If the two Tx chains are triggered to switch between two different band pairs (e.g., band A + band B->band C+ band D), and when the two UL transmissions on band C and band D are at least partially overlapped in time domain, the T_offset of timeline T₀-T_offset for switching is determined based on the switching gap defined for a single Tx switching in [8, TS 38.101-1].

·       T0 is the starting point of the earlier transmission among the two uplink transmissions (band C + band D). This does not change the definition of T0 in current specifications.

·       FFS: whether any specification impact is needed.

Final summary in R1-2312695.

 RAN1#116

8.88      Maintenance on Multi-Carrier Enhancements for NR

[116-R18-MC_Enh] – Hiroki (NTT DOCOMO)

Email discussion on multi-carrier enhancement for NR

-        To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2400040         Remaining issues on Multi-Carrier Enhancements for NR              Spreadtrum Communications

R1-2400136         Maintenance of Rel-18 Multicarrier Enhancements    Huawei, HiSilicon

R1-2400198         Remaining issues on Rel-18 multi-carrier enhancements              Lenovo

R1-2400223         Maintenance on Multi-Carrier Enhancements for NR  vivo

R1-2400293         Maintenance on Multi-Carrier Enhancements for NR  ZTE

R1-2400311         Remaining issues on  Multi-carrier enhancements for NR              CMCC

R1-2400413         Maintenance on Multi-Carrier Enhancements for NR  CATT

R1-2400542         Remaining issues on Multi-Carrier Enhancements for NR              xiaomi

R1-2400596         Remaining issues in multi-carrier enhancement for NR              OPPO

R1-2400654         On Rel-18 MC-DCI scheduling       Nokia, Nokia Shanghai Bell

R1-2400681         Maintenance on Multi-Carrier Enhancements for NR  Langbo

R1-2400712         Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI         Samsung

R1-2400764         Remaining issues on SCell dormancy indication by DCI format 0_3/1_3 Fujitsu

R1-2400993         On maintenance issues for Rel-18 MC enhancements Apple

R1-2401095         Maintenance on multi-carrier enhancements NTT DOCOMO, INC.

R1-2401140         Maintenance for Rel-18 multi-carrier enhancements   Ericsson

R1-2401289         On maintenance for multi-carrier enhancement           MediaTek Inc.

R1-2401323         Remaining issues on multi-cell scheduling with single DCI      LG Electronics

R1-2401589         Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI         Moderator (Lenovo)

From Tuesday session

Agreement

Adopt following TP for TS38.213.

·       Change reason: Unicast DCI formats do not include DCI format 1_3 and 0_3.

·       Change summary: Add DCI format 1_3 and 0_3 in unicast DCI format list.

·       Consequence if not approved: Incomplete unicast DCI format list.

Agreement

·       Adopt the following TP for sub-clause 9.1.2.1 in TS38.213.

Agreement

A UE does not expect a DCI format 0_3/1_3 schedules an SCell with valid FDRA value and indicates the SCell to switch to dormant BWP.

Conclusion

For a cell scheduled by DCI format 0_3 with valid FDRA value, UE does not expect that OLPC/CAPC/TPMI/SRI in the DCI format indicates a code point that does not correspond to a configuration for the cell.

·       No spec impact.

Conclusion

FDRA validity for a cell is determined based on the indicated BWP of the cell.

·       No spec impact.

Agreement

·       Adopt the following TP to 38.212 for DMRS sequence initialization in DCI format 0_3:

Agreement

·       TP1 in section 8 of R1-2401589 is agreed for TS38.214.

R1-2401590         Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI         Moderator (Lenovo)

From Wednesday session

Agreement

·       Adopt the following TP covering multi-cell scheduling in TS38.300.

--------------- Start of TP -------------

10.X          Multi-cell scheduling by a single DCI

Multi-cell scheduling by a single DCI allows the PDCCH of a serving cell to schedule PDSCH(s)/PUSCH(s) on one or more serving cells with the single DCI but with the following restrictions:

-          When a serving cell is configured with a PDCCH which schedules PDSCH(s)/PUSCH(s) on a cell set, the PUSCH/PDSCH on serving cells in the cell set is always scheduled by a PDCCH on the serving cell;

-          When PCell is configured with a PDCCH which schedules PDSCH(s)/PUSCH(s) on serving cells in a cell set, that PCell’s PDSCH and PUSCH cannot be scheduled by a PDCCH on an SCell;

-          When an SCell is configured with a PDCCH which schedules PDSCH(s)/PUSCH(s) on serving cells in a cell set, PCell is not included in the cell set;

-          The scheduling PDCCH and the scheduled PDSCH(s)/PUSCH(s) can use the same or different numerologies;

-          The co-scheduled PDSCH(s) with a PDCCH use the same numerology.

-          The co-scheduled PUSCH(s) with a PDCCH use the same numerology.

--------------- End of TP -------------

Send an LS to RAN2 to convey the above TP. Final LS is approved in:

R1-2401716         LS on TS38.300 TP for Multi-cell scheduling in Rel-18              RAN1, NTT DOCOMO

Agreement

·       TP2 for TS38.213 in Section 8 of R1-2401590 is agreed in principle. Editor to provide final TP.

R1-2401591         Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI         Moderator (Lenovo)

From Friday session

Agreement

• When a PDCCH MO that provides a DCI format 1_3 is before active UL BWP change on the PUCCH cell, and the PUCCH indicated by the DCI format 1_3 is to be transmitted after the active UL BWP change on the PUCCH cell, the corresponding HARQ-ACK information for the DCI format 1_3 is skipped.
• FFS: When a PDCCH MO that provides a DCI format 1_3 is before an active DL BWP change on a cell of co-scheduled cells by the DCI format 1_3, and the DCI format 1_3 does not trigger the active DL BWP change for the cell, and the PUCCH indicated by the DCI format 1_3 is to be transmitted after the active DL BWP change on the cell,

o   For type 2 codebook for generating the second sub-codebook, the corresponding HARQ-ACK information for that cell with BWP switching is generated with NACK bit

o   For type 1 codebook and for type 2 codebook for generating the first sub-codebook, follow the legacy behaviour (the corresponding HARQ-ACK information for that cell with BWP switching is skipped)

Final summary in R1-2401848.

R1-2401510         Summary of discussion on Multi-carrier UL Tx switching scheme  Moderator (NTT DOCOMO, INC.)

From Tuesday session

Agreement

·       Agree on following TP

Conclusion

Following scheduling restriction is covered by section 6.1.6 in TS38.214.

·       For UL Tx switching, if an UL transmission with starting symbol at T0 is scheduled to a UE, the UE is not expected to be scheduled with another UL transmission overlapping with the first UL transmission in time and resulting in interruption on the first UL transmission by a DCI arriving later than T0-Toffset.

R1-2401639         Summary#2 of discussion on Multi-carrier UL Tx switching scheme  Moderator (NTT DOCOMO, INC.)

From Wednesday session

From AI 5

R1-2400007         LS on UL Tx Switching   RAN2, Huawei

Agreement

• RAN1 replies to RAN2 LS in R1-2400007 as below.
• RAN1 confirms that the first RAN2 agreement in the LS R1-2400007/R2-2313959 has no issue from RAN1 perspective, except for a case where Rel-18 UL Tx switching is configured with band combination {A, B} to a UE reporting support of UL Tx switching for band combination {A, B, C} /{A, B, C, D} and no UL-MIMO on band A nor band B. For the case, RAN1 continues to discuss it.

Final LS is approved in:

R1-2401776         Reply LS on UL Tx switching       RAN1, NTT DOCOMO

Final summary in R1-2401802.

 RAN1#116-bis

8.33      Maintenance on Multi-Carrier Enhancements for NR

[116bis-R18-MC_Enh] – Hiroki (NTT DOCOMO)

Email discussion on multi-carrier enhancement for NR

-        To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2402032         Maintenance of Rel-18 Multicarrier Enhancements    Huawei, HiSilicon

R1-2402093         Remaining issues on Multi-Carrier Enhancements for NR              Spreadtrum Communications

R1-2402163         Maintenance on Multi-Carrier Enhancements for NR  ZTE

R1-2402213         Maintenance on Multi-Carrier Enhancements for NR  vivo

R1-2402301         Maintenance of multi-carrier enhancement for NR      OPPO

R1-2402359         Maintenance on Multi-Carrier Enhancements for NR  CATT

R1-2402433         Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI         Samsung

R1-2402527         Maintenance on Multi-Carrier Enhancements for NR  Langbo

R1-2402584         Remaining issues on Rel-18 multi-carrier enhancements              Lenovo

R1-2402640         Remaining issues on Multi-Carrier Enhancements for NR              Xiaomi

R1-2402932         On Rel-18 MC-DCI scheduling       Nokia

R1-2403114         Remaining issues on multi-cell scheduling with single DCI      LG Electronics

R1-2403171         Maintenance on Rel-18 multicarrier enhancements     Qualcomm Incorporated

R1-2403220         Maintenance on Multi-Carrier Enhancements for NR  NTT DOCOMO, INC.

R1-2403269         Maintenance for Rel-18 multi-carrier enhancements   Ericsson

R1-2402068         Correction on DCI format 1_3 with SRS carrier switching              ZTE

R1-2403477         Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI         Moderator (Lenovo)

From Monday session

Agreement

·       Adopt following TP for TS38.214.

Agreement (in principle)

Final TP to be decided by the editor.

·       TP2 on TS38.213:

Agreement

For a UE configured with a set of cells by MC-DCI-SetofCells, when a cell in the set of cells is dormant or deactivated and the cell is neither the scheduling cell nor the reference cell for the set of cells, the UE can receive a DCI format 1_3/0_3 that schedules serving cells including the cell;

·       The UE does not expect a PDSCH or a PUSCH scheduled on the cell.

·       The fields of DCI format 1_3 corresponding to the cell can be reinterpreted for indicating SCell dormancy indication, the index of the enhanced Type-3 HARQ-ACK codebook or the value of slot level offset l.

o   The UE checks the field value of the cell in the DCI format 1_3.

·       Note: FDRA field of the cell in the DCI format 1_3/0_3 is set to invalid.

Conclusion

There is no consensus to support search space sharing for DCI format 0_3/1_3.

R1-2403478         Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI           Moderator (Lenovo)

R1-2403479         Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI         Moderator (Lenovo)

From Friday session

Agreement

·       Keep the wording of TS38.212-i20 unchanged in regards to the usage of invalid FDRA for determination of scheduled / non-scheduled cells.

·       RAN1 confirms that repurposed-based indication of {SCell dormancy, enhanced Type-3 HARQ-ACK CB, HARQ retransmission} is supported regardless of whether ScheduledCellCombo-ListDCI-1-3 is configured or not.

o   No RAN1 spec impact.

Agreement

Adopt TP3 in Section 8 of R1-2403479 for TS38.214.

Conclusion

For a cell scheduled by DCI format 0_3/1_3 with valid FDRA value, UE does not expect that a Type-1B field in the DCI format indicates a code point that does not correspond to a configuration for the cell.

·       No RAN1 spec impact.